-
Notifications
You must be signed in to change notification settings - Fork 865
State not retaining when the App reload/Kill the App from Background #1102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
+1 |
Lets see what your reducer looks like |
I have the same problem, any solution you found? It only happens to me on Android, In ios it works perfectly |
Your data stored not in database. It is stored in AsyncStorage |
@whalemare AsyncStorage uses a database
|
I'm seeing this problem in the wild too and it seems to be related to large store states. How big is your store? We also have nested persist configs and combined reducers so I'm not sure if that is affecting the issue. |
I had this issue too, i recommend you to check the data that you save and to save it as little as possible. |
This happens because of using It is not relevant to the size of the object in that case, manually calling |
When your store is large (>4 Mb) you're more likely to run out of memory on Android. |
having the same problem in 2023, version 6.0.0, any solutions? |
Same problem, any solution ? |
any solutions??? |
I do have the same issue, but not using async storage, I'm using file based redux-persist-filesystem-storage. |
same here also |
I am using redux for maintaining the state in my App, Currently i am having issue in Android OS,
I am using the below dependencies
Below is my Redux configurations
The issue i am facing is the data is saved in state when the app is active, If i am killing the app or app hot reload the app i am not getting the data saved in the state.
I tried to see the db file in terminal using the below comand
adb -d shell "run-as com.appid ls /data/data/com.appid/databases/
It is not showing any list, What might be the problem? Can anyone suggest
The text was updated successfully, but these errors were encountered: