I’m wondering if changing the slug and Expo account wipes asyncstorage for an app? I released an update for an app recently on the Play Store and all user data was deleted for whoever downloaded the update.
I had published under a new Expo account and changed the slug
Correct, your app’s data is sandboxed based on the author and slug of the app. This prevents apps from interfering with each others’ data.
Thanks @ben , maybe this can be added to the docs to prevent other people from running into this issue?
If I create another binary file and release an update with the old slug and old Expo account. Will it still have the original user data (from before the app update was released)?
Hi, yeah, maybe we could make it clearer in the docs for AsyncStorage specifically. It’s hard to know where we would document that exactly since AsyncStorage is an upstream API and doesn’t live in our docs.
Yes, if the user installs your update over their old copy on their phone, the old AsyncStorage data for your previous slug should still be there.
Hi, I haven’t changed the slug, or the author, but bumped the sdk version from 29 to 35 – when I upgrade the app, I also don’t have any of the data
Hi
It seems that the location was changed, so it would probably be best to move to SDK 33 or 34 first, so that the migration is run. See the following post:
Does that mean, that I need to wait until every user, updates the app, before I can release SDK 35?