bamlab / bamlab/redux-enhancer-react-native-appstate

Some kind of conflict with redux-persist

Open
#8 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
89
Forks
7
PR merge metrics
No merged PRs in 30d

Description

Love this package -- simple and useful, and I use it in all RN apps I'm on.

Just found a nasty gotcha, though, in the context of how the redux-persist plays with redux-enhancer-react-native-appstate.

Long story short, I'm using `redux-persist@5.10.0` with `redux-enhancer-react-native-appstate@0.3.1` and previously was **not** including `appState` (the name I assigned the reducer which hooks into `redux-enhancer-react-native-appstate` action types) into `redux-persist`'s `blacklist` property of its `persistConfig`.

Result: My app wouldn't properly persist on `Release`-derived builds.

I added `appState` into the `blacklist` and all returned to being well. Hopefully this helps someone ¯\_(ツ)_/¯

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the interaction between redux-persist@5.10.0 and redux-enhancer-react-native-appstate@0.3.1 in a React Native Release-derived build. Compare persistence behavior with and without appState in persistConfig.blacklist. Done means the conflict is resolved or clearly documented with a verified configuration and regression coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native, redux
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.