-
Notifications
You must be signed in to change notification settings - Fork 866
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
Getting error redux-persist: rehydrate for "root" called after timeout #717
Comments
The same happens to me after upgrading to v5.7.1 |
Same story here :/ |
I just downgraded version to 5.6.12 and still not working |
@Avid21 Reverting back to 5.6.12 worked for me. |
How to downgrade? Uninstall and re-install? |
Use semver |
@NichAga Yes, it should work. I was using Remote JS debugging. I stopped it and hence naturally it's working now. |
Same here! =( |
Thanks @NichAga I figured it out. Just downgrade and keep working for the moment guys. |
Yes, getting the same error. Reverting to 5.6.12 worked |
Worked after switching back to redux-persist@5.6.12 |
Same 😡 |
Switch back to 5.6.12 works! |
@jarvisluong yup im switch back to ~5.6.0 |
apologize for the churn here, v5.7.2 resolves the issue. tests missed the issue on 5.7.1 as it was a console.error, not an actual exception |
@rt2zz I still have the same error after update to v5.7.2. |
I don't have this error with v.5.7.2. @RodolfoSilva are you sure that you upgrade version? You can check this in npm.lock or yarn.lock file. |
@sytolk, Yes, I'm use the latest version and still have the error. This error only happens when I use the debug in the first time.
|
I can confirm it's working with 5.7.2. |
react-native: v0.53.0 Ok, that fixed not the error. I downgraded to |
I have to say I've been stuck in this problem for a while now and it was my fault. I forgot to return an action on an Epic. I hope this helps anyone |
I am stuck with this issue on my recently expo detached project. My state is never persisted regardless of remote debugging, and occasionally I get the error like the OP. Expo: 24.0.0 On an up note, thank you very much for your work! |
Same as @calanti
|
I was getting the same error on redux-persist version 5.9.1. It was working fine until I put the
But then I switched back to using the
|
Thanks for the insight and yes I am whitelisting, but blacklisting is not really a maintainable solution for me, too many recuders and I only need 2 whitelisted. Hopefully this can help the devs identify the issue though! |
I have just created a new project with Expo and can not get this work either. |
I get this issue with 5.9.1. Potentially related to this issue with setTimeout in React Native facebook/react-native#4470 |
I was getting the same error. The issue was the emulators date and time weren't synchronised with my computer's. Make sure your date and time is the same between both |
What @Gustash recommends + be sure your time zones are also aligned. |
I just needed to restart my emulator. |
This one solve my problem |
try this
work for me |
Same problem to react-native 0.60.0 |
The only way we could have a cleanup and a persistence that still works afterward is by doing that hack Can we make this bug official (reopening the ticket) somehow and work on that ? |
Still happening with React Native version 0.60.0 and redux-persist 5.10.0. I tried the suggestion with timeout being set to 0, not working at all. |
+1 |
I got this error when the device I was testing on didn't have internet connectivity, and went away when it did. Could be related to the time mismatch issue @Gustash noted above. |
Got this error on |
Thank you for reminding me!This worked for me! |
For me issue appeared after upgrading RN to 0.60.0 and react-native-navigation to v4 and was resolved after I replaced previously recommended by wix android run script
with the standard script
|
What will be the implications of doing this? |
This issue was been there for a while, i tried a lot fixing it and finally @Gustash solution resolves it, thank you very much 👍 |
FYI, setting timeout to null instead of 0 will not fix this issue. Timeout must be a number. You can run the tests and verify if you want. Here's what the test output says when timeout is null:
|
Just to make this clear, is this a dev only issue (meaning that if we don't use any timeout values users won't have issues in production will they?) |
This issue exists in all environments. |
@SudoPlz Definitely an issue affecting production. I recommend thoroughly combing through the redux-persist code. Complete and total data erasure on production clients will be very frustrating, and it's a very good idea to understand the data storage layer fully. If we weren't planning on moving away from react-native to native, we would honestly re-write our own lib to handle this because redux-persist has a few issues and it's not actively maintained anymore. |
as the package is not maintained anymore we could at least have some examples on how to migrate the data to another source, it will affect tons of projects. |
As best I can tell that would require writing an alternative to redux-persist, understanding its persistence interaction with the file system / async storage, then writing a migration guide. That seems an unreasonable expectation of an author who abandoned the old project. Much more likely that a new project taking over the problem of redux-persistence would write a guide / utility for migrating TO their new project. |
not working for me and 6.0.0 as well |
Still actual |
Lo que funcionó para mi fue pasar directamente en el reducer el persistedReducer const persistedReducer = persistReducer(persistConfig, rootReducer); const store = configureStore({ |
Thanks, @hryer |
I am using expo sdk version 25
My code is as below
reducers.js
configureStore.js
App.js
The text was updated successfully, but these errors were encountered: