I've noticed that persistAuthConfig might not be be saving the isLoggedIn flag that app.js uses to decide whether to show the protected routes + their components due to the way that redux persist reconciles state during a rehydration (https://github.com/rt2zz/redux-persist#state-reconciler). Whitelisting currentUser and isLoggedIn separately seem to fix the issue
Lmk what you think, since you've worked with persist more than I have
I've noticed that
persistAuthConfig
might not be be saving theisLoggedIn
flag that app.js uses to decide whether to show the protected routes + their components due to the way that redux persist reconciles state during a rehydration (https://github.com/rt2zz/redux-persist#state-reconciler). WhitelistingcurrentUser
andisLoggedIn
separately seem to fix the issue Lmk what you think, since you've worked with persist more than I have