Zack Story

note: we can also go one step further and remove the react-native injection and require people to require navigation components straight out of navigation-rfc

@asciiman redux persist assumes state is a plain object (or really any type of Map as long as the correct config is provided). This assumption is useful for making persistence...

can you try again on v5.3+, we now detect if the substate is an array and if so skip shallow merging state. i.e. this issue should be resolved.

@SaltedBlowfish @sunweiyang that works, or the second more formal but slightly more involved method is to add a [migration](https://github.com/rt2zz/redux-persist/blob/master/docs/migrations.md). You can explicitly delete keys in the migration. That said this...

are you using android? react native AsyncStorage has a bug with android when the debugger is open causing this to happen. As you can see the persist is timing out...

hm, then possibly a bug with `storageSession`? You could try using localForage (https://github.com/localForage/localForage) and see if that works?

ah interesting, so session storage is failing - that explains the behavior. We need to figure out why. That means this line is failing: https://github.com/rt2zz/redux-persist/blob/master/src/storage/getStorage.js#L35 are you running this in...

Ok I see REHYDRATE is being called twice, can you make sure you are on the latest version of redux persist? I believe 5.7.x may have had a bug causing...

@atav32 you are seeing persist dispatched twice when there is no prior storage? That is definitely a bug, but I dont see how that can happen as we only allow...

@diegolaciar it looks like you are using redux-persist v4, but somehow also getting PersistGate which is only available in (and compatible with) v5. You can read about the upgrade here:...