localForage and getStoredState from Redux Persist

Using getStoredState while in incognito mode or with cookies disabled in Safari causes the store to never be made available. localForage rejects it’s promise with the SecurityError thrown by Safari.

Since understanding how redux-persist and localForage interplay in this scenario and how to resolve that is too large a task for me I simply revert to not using localForage if I can get an error by trying to access localStorage like so:

let enableLocalForage = true;
try {
  localStorage.setItem('__u', 'u');
}
catch (e) {
  // proxy to figure out if we're in an incompatible environment for localForage
  // since redux-persist doesn't play nice when localForage fails to start
  enableLocalForage = false;
}

const persistConfig = {
  storage: enableLocalForage ? localForage : null,
};

This stops my app from breaking when it starts but the console does get littered with warnings while in this mode.

[dviry]

Just wondering - looking one step back - wouldn’t localForage by itself fail when localStorage is not available and simply go to the next driver? Wouldn’t just defining memoryStorage as the fallback driver solve those issues (and still be within localForage functionality)?

PS: we could also simply extend isLocalStorageValid to actually try to call .setItem() and thus invalidate localStorage in case of Safari (or any other) errors.

[modosc]

update: i published https://github.com/modosc/redux-persist-memory-storage as a general purpose solution - we’ve had to use this pattern for clients with cookies or localstorage disabled.