React-Native AsyncStorage: What exactly does 'clear()' function clear?
up vote
1
down vote
favorite
The official docs about .clear()
are not very clear to me. They say the following:
Erases all AsyncStorage for all clients, libraries, etc. You probably don't want to call this; use removeItem or multiRemove to clear only your app's keys. Returns a Promise object.
Can anybody explain, what 'all clients' exactly means in this context? For me it sounds like other RN-Apps stores could be affected too, I just can't imagine that this would even be possible.
react-native store asyncstorage
add a comment |
up vote
1
down vote
favorite
The official docs about .clear()
are not very clear to me. They say the following:
Erases all AsyncStorage for all clients, libraries, etc. You probably don't want to call this; use removeItem or multiRemove to clear only your app's keys. Returns a Promise object.
Can anybody explain, what 'all clients' exactly means in this context? For me it sounds like other RN-Apps stores could be affected too, I just can't imagine that this would even be possible.
react-native store asyncstorage
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
The official docs about .clear()
are not very clear to me. They say the following:
Erases all AsyncStorage for all clients, libraries, etc. You probably don't want to call this; use removeItem or multiRemove to clear only your app's keys. Returns a Promise object.
Can anybody explain, what 'all clients' exactly means in this context? For me it sounds like other RN-Apps stores could be affected too, I just can't imagine that this would even be possible.
react-native store asyncstorage
The official docs about .clear()
are not very clear to me. They say the following:
Erases all AsyncStorage for all clients, libraries, etc. You probably don't want to call this; use removeItem or multiRemove to clear only your app's keys. Returns a Promise object.
Can anybody explain, what 'all clients' exactly means in this context? For me it sounds like other RN-Apps stores could be affected too, I just can't imagine that this would even be possible.
react-native store asyncstorage
react-native store asyncstorage
asked Nov 8 at 9:30
Christoph Göttert
11518
11518
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
It means everything that was stored by apps in asyncstorage will be cleared and yes it includes not only yours but other apps too it is clear from the documentation's this line
Erases all AsyncStorage for all clients, libraries, etc. You probably
don't want to call this use removeItem or multiRemove to clear only
your app's keys.
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
add a comment |
up vote
0
down vote
means that it will clean everything you have added using setItem
.
other RN-Apps stores could be affected too?
R/ No, AsyncStorage
concat a appId
(or something like that) to your setItem key
to prevent remove info from another app.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It means everything that was stored by apps in asyncstorage will be cleared and yes it includes not only yours but other apps too it is clear from the documentation's this line
Erases all AsyncStorage for all clients, libraries, etc. You probably
don't want to call this use removeItem or multiRemove to clear only
your app's keys.
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
add a comment |
up vote
0
down vote
It means everything that was stored by apps in asyncstorage will be cleared and yes it includes not only yours but other apps too it is clear from the documentation's this line
Erases all AsyncStorage for all clients, libraries, etc. You probably
don't want to call this use removeItem or multiRemove to clear only
your app's keys.
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
add a comment |
up vote
0
down vote
up vote
0
down vote
It means everything that was stored by apps in asyncstorage will be cleared and yes it includes not only yours but other apps too it is clear from the documentation's this line
Erases all AsyncStorage for all clients, libraries, etc. You probably
don't want to call this use removeItem or multiRemove to clear only
your app's keys.
It means everything that was stored by apps in asyncstorage will be cleared and yes it includes not only yours but other apps too it is clear from the documentation's this line
Erases all AsyncStorage for all clients, libraries, etc. You probably
don't want to call this use removeItem or multiRemove to clear only
your app's keys.
answered Nov 8 at 10:12
Ammar Tariq
758
758
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
add a comment |
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
Wow this is crazy, so potentially every App can delete my whole async-storage? This seems horrible from a security perspective. Isn't async storage sandboxed for every App by it's app-id?
– Christoph Göttert
Nov 8 at 13:34
add a comment |
up vote
0
down vote
means that it will clean everything you have added using setItem
.
other RN-Apps stores could be affected too?
R/ No, AsyncStorage
concat a appId
(or something like that) to your setItem key
to prevent remove info from another app.
add a comment |
up vote
0
down vote
means that it will clean everything you have added using setItem
.
other RN-Apps stores could be affected too?
R/ No, AsyncStorage
concat a appId
(or something like that) to your setItem key
to prevent remove info from another app.
add a comment |
up vote
0
down vote
up vote
0
down vote
means that it will clean everything you have added using setItem
.
other RN-Apps stores could be affected too?
R/ No, AsyncStorage
concat a appId
(or something like that) to your setItem key
to prevent remove info from another app.
means that it will clean everything you have added using setItem
.
other RN-Apps stores could be affected too?
R/ No, AsyncStorage
concat a appId
(or something like that) to your setItem key
to prevent remove info from another app.
answered Nov 8 at 13:32
jose920405
5,53122849
5,53122849
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53204859%2freact-native-asyncstorage-what-exactly-does-clear-function-clear%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password