Immutable list rehydrating as a map, after upgrading to react-native 0.44.0

[cbjs]

Description

use redux / immutable for state.
redux-persist / redux-persist-transform-immutable for state persistence.

Every is good with react-native 0.43.4.
Immutable list rehydrating as a map, after upgrading to react-native 0.44.0

Reproduction Steps and Sample Code

import { persistStore, autoRehydrate } from 'redux-persist';
import immutableTransform from 'redux-persist-transform-immutable';

const configureStore = () => {
 const store = createStore(
 reducer,
 composeEnhancers( applyMiddleware(...middlewares), autoRehydrate() )
 );

 return store;
}
const store = configureStore();

persistStore(store, {
 storage: AsyncStorage,
 transforms: [immutableTransform()]
});

Solution

No workaround.
May this issue is related to packager updates in 0.44.0
related issues: rt2zz/redux-persist-transform-immutable#21
glenjamin/transit-immutable-js#32

Additional Information

• React Native version: [0.44.0]
• Platform: [Android]
• Development Operating System: [Linux]
• Dev tools: [android-23]

[brunolemos]

Hi @cbjs,

Problem

This issue was caused by multiple versions os immutable being installed, like pointed out on this issue: glenjamin/transit-immutable-js#32

Solution

Upgrade react-native to 0.45, as immutable dependency has been removed in this commit.

Run: npm i --save react-native@0.45.0-rc.2 react@16.0.0-alpha.12

Alternative solution

Ensure you only have 1 version of immutable installed. Change your immutable version to the same as react native is using (npm i --save immutable@3.7.6). Check for other packages requiring a specific version of immutable as well. Make a PR to them removing it or moving to peerDependencies if necessary. (if you use npm5 or yarn, you can check the lock file to see all immutable versions and who required them)

Feel free to close this issue if it works for you.
Thanks!

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.