Closed jln-dk closed 6 years ago
Closing due to lack of activity on this issue. Please reopen if further discussion is required.
This is happening also to our app. This issue should be not closed because all new users of this library should be aware of this before they decide to use it.
I don't believe this is a bug with this library. No one has been able to reproduce it or suggest the cause of the issue.
It possible that it's caused by redux-persist or by an implementation detail within your app (perhaps you're calling 'purge' on the redux-persist data?)
If you can create a reproducible example, or identify the cause of the issue, please share it here.
@robwalkerco Nope it is not caused by an implementation detail like calling purge
, because I don't call purge
in my app. I use the latest version from both redux-persist and your library.
No reproducible example but this happens randomly. Do you know what can cause this persist/REHYDRATE
error ?
No such file '/var/mobile/Containers/Data/Application/FF7ABD38-39F0-4E2B-872A-B6691F47B757/Documents/persistStore/persist-[name-of-my-app]'
I suspect it is linked to rn-fetch-blob
iOS implementation.
Introduction
We are building a React Native app, and we are using redux-persist together with redux-persist-filesystem-storage to store data on the phone.
The issue
We are experiencing that sometimes after an app update (via TestFlight and Play Store) all the app data just is erased. The app is simply back to initial state. This can happen for both iOS and Android.
Steps to reproduce
Well, this is where it get's annoying.. We haven't yet been able to get the exact steps to reproduce the issue. It just happens sporadically. We have around 100 beta testers, and ~20 people have reported this issue. Both on iOS and Android, and there was no link between a specific app update version or anything.
Similar issues
We have of course looked around on GitHub, trying to find similar issues. At first we thought https://github.com/rt2zz/redux-persist/issues/199 was our issue, so that's why we switched to redux-persist-filesystem-storage from AsyncStorage. But that didn't help. And it looks like other people are still experiencing it as well: https://github.com/robwalkerco/redux-persist-filesystem-storage/issues/2
Additional information
redux-persist
version: 4.9.1redux-persist-filesystem-storage
version: 1.10Final note
Although this issue is somewhat vaguely described, I'm submitting it to raise awareness, because we think it's a rather important issue if it really IS an existing bug. Maybe someone out there is looking for help with the same issue - so here it is.