Error: No available storage method found

[jasan-s]

I am still getting an error : (node:12884) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 6): Error: No available storage method found. I'm using v1.50
Update: The error actually only occurs when using react-snapshot lib

[lieut-data]

Assuming we have similar root causes, I traced the unhandled promise rejection warning to the following:

localForage/src/utils/executeTwoCallbacks.js

Lines 1 to 11 in f66bb7b

	function executeTwoCallbacks(promise, callback, errorCallback) {
	if (typeof callback === 'function') {
	promise.then(callback);
	}
	if (typeof errorCallback === 'function') {
	promise.catch(errorCallback);
	}
	}
	export default executeTwoCallbacks;

The unhandled promise rejection comes from the promise returned (but ignored) by invoking .then above. In my case, this path was reached by passing a callback to localforage.ready:

localforage.ready(() => {
    // ...
}).catch(() => {
    // ...
});

I can work around this by instead relying exclusively on the promise, sidestepping the bug in executeTwoCallbacks above:

localforage.ready().then(() => {
    // ...
}).catch(() => {
    // ...
});

To fix executeTwoCallbacks properly, I suspect one would want to preserve the promise chain back to all the callers of this utility method, returning the promise at each step vs. branching as above.

[951565664]

Is this a custom errorMessage? What does this error message mean? My monitoring system caught this error, but I don't know how to reproduce it.

[951565664]

I want to know when this problem will occur?

[thgreasi]

Hey, Yes this is a custom error message and it is thrown when... No available storage method is found. You can reproduce by using private browsing mode and also disabling cookies and in general turn on all the browser settings that will prevent sites to store anything locally. In case you still want to use the same code, even if localforage will not be able to save anything, you can use the localforage-memoryStorageDriver. See: https://github.com/localForage/localForage-memoryStorageDriver

…

On Fri, Mar 15, 2019, 09:08 小哈husky ***@***.***> wrote: I want to know when this problem will occur? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#722 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPF1XNNTygxJe3wZACrcLTo_MZnHRKCks5vW0bigaJpZM4O2ROa> .

[AndrewBogdanovTSS]

@thgreasi localForage-memoryStorageDriver looks interesting but documentation doesn't provide a full example of using it. Maybe you could provide an example of how a situation of not having any local storage options can be handled with the help of it? Can it be somehow picked up by localForage automatically? As far as I understand the logic behind using it is:

1. Detect if any storage option is supported.
2. If not - activate localForage-memoryStorageDriver
   Should these steps be done manually or it will be handled by localForage automatically after adding a dependency?

My Sentry system also tracks this issue for a lot of users but I can't understand what they had to do in order to get such error? From my point of view - it's really not that easy to turn off all the storing mechanisms in modern browsers nevertheless I'm getting this issue from users with Chrome, Safari and Firefox, all recent browser versions.
The error is triggered in this part of the code:

                self._driver = driver._driver;
                setDriverToConfig();
                self._wrapLibraryMethodsWithReady();
                self._initDriver = initDriver(supportedDrivers);
            });
        })["catch"](function () {
            setDriverToConfig();
            var error = new Error('No available storage method found.'); // This line triggers an error
            self._driverSet = Promise$1.reject(error);
            return self._driverSet;
        });

[AndrewBogdanovTSS]

I was able to reproduce the issue by manually disabling Cookies in the global Chrome settings https://take.ms/nXAWX
@thgreasi is there a way to detect whether storage options are available in localForage?

[Chris1234567899]

Same issue here. In my case, some clients probably are using some plugin or addon in firefox that blocks cookies and therefore breaks localforage.

For a temporal workaround I added
https://www.npmjs.com/package/localforage-driver-memory
to the driver list.
At least the app does not crash then and I can show them some popup warning to deactivate their plugin.

Waiting for a "real" fix though ;-)

[AndrewBogdanovTSS]

@Chris1234567899 could you share your setup regarding localforage-driver-memory ? Do you import it with a static import or it can be dynamically imported only for users that doesn't allow cookies?

[salidean]

@AndrewBogdanovTSS give this a try:

import * as localforage from 'localforage';
import * as memoryDriver from 'localforage-driver-memory';
 
localforage.defineDriver(memoryDriver);
localforage.setDriver(memoryDriver._driver);

[Etheryte]

It would be nice to make this error try-catchable. Our current use case is essentially

import localforage from 'localforage';

let instance: LocalForage;
try {
  instance = localforage.createInstance({ ... });
} catch (error) { ... }

However with this setup, the above error can't be caught.
Users disabling cookies & local storage, using private browsing, etc are all valid use cases and it would be nice to support them.

[AndrewBogdanovTSS]

@salidean what do you think about such strategy?

import * as localForage from 'localforage'
import * as memoryDriver from 'localforage-driver-memory'

localForage.defineDriver(memoryDriver)
localForage.setDriver([localForage.LOCALSTORAGE, localForage.INDEXEDDB, localForage.WEBSQL, memoryDriver._driver])

I want to fallback to memoryDriver only when all others aren't available

[beshkenadze]

The error is still valid for SSR :(

[smithki]

I've encountered this issue during unit tests that depend upon localforage, even with the following snippet:

import * as localforage from 'localforage';
import * as memoryDriver from 'localforage-driver-memory';
 
localforage.defineDriver(memoryDriver);
localforage.setDriver(memoryDriver._driver);

For the life of me I cannot find where the code is throwing, but I have a feeling the error is uncatchable without modifying the localforage source code.

[BernardA]

Just to second @beshkenadze as I still have the issue after implementing the proposal from @AndrewBogdanovTSS on my Next js app.

[waleedarshad]

localforage

@BernardA have you found any solution. What workaround did you try out?

[BernardA]

@waleedarshad This was many moons ago. I can't recall at all. Sorry.

[beshkenadze]

@waleedarshad you have to disable a persist reducer for the server-side rendering, something like that:

const persistedReducer = persistReducer(
    persistOptions,
    offlineEnhanceReducer(rootReducer),
);

if (isServer) {
    store = createStore(
        rootReducer,
        preloadedState,
        applyMiddleware(sagaMiddleware, offlineMiddleware),
    );
} else {
    store = createStore(
        persistedReducer,
        preloadedState,
        composeEnhancers(
            offlineEnhanceStore,
            applyMiddleware(sagaMiddleware, offlineMiddleware),
        ),
    );
}

[sherl0cks]

I hit this issue when using aws amplify datastore. At one point I scoured their code and found that the root cause was that jsdom does not provide indexeddb. You can use https://www.npmjs.com/package/fake-indexeddb to solve this. So long as you import 'fake-indexeddb/auto'; before the code instantiating localforage runs, it should alleviate the problem.

[yangfei4913438]

I'm using nextjs, and I'm getting the same error. But I found out that it was caused by a timed task using localforage while running on the server side. Once I disabled the timer from running on the server side, the error went away.

[gaozhidf]

you can define a custom driver like emptyLocalForageDriver, and set it as default when window is undefined.

const emptyLocalForageDriver = {
  // ref: https://localforage.github.io/localForage/#driver-api-definedriver
  _driver: 'emptyLocalForageWrapper',
  _support: true,
  _initStorage: function(options: any) {
      // Custom implementation here...
  },
  clear: function(callback: any) {
      // Custom implementation here...
  },
  getItem: function(key: any, callback: any) {
      // Custom implementation here...
  },
  iterate: function(iteratorCallback: any, successCallback: any) {
      // Custom implementation here...
  },    
  key: function(n: any, callback: any) {
      // Custom implementation here...
  },
  keys: function(callback: any) {
      // Custom implementation here...
  },
  length: function(callback: any) {
      // Custom implementation here...
  },
  removeItem: function(key: any, callback: any) {
      // Custom implementation here...
  },
  setItem: function(key: any, value: any, callback: any) {
      // Custom implementation here...
  }
}

export function setLocalForageDriver(storageType: string) {
  // set storage to https://trytobe.top 
  if (typeof window === "undefined") {
    storageType = "undefined";
  }
  switch (storageType) {
    case "indexeddb":
      // use indexeddb
      localForage.setDriver(localForage.INDEXEDDB);
      break;
    case "localstorage":
      // use localstorage
      localForage.setDriver(localForage.LOCALSTORAGE);
      break;
    default:
      localForage.defineDriver(emptyLocalForageDriver as LocalForageDriver);
      localForage.setDriver('emptyLocalForageWrapper');
      break;
  }
}

[abdulsalamcodes]

I hit this issue when using aws amplify datastore. At one point I scoured their code and found that the root cause was that jsdom does not provide indexeddb. You can use https://www.npmjs.com/package/fake-indexeddb to solve this. So long as you import 'fake-indexeddb/auto'; before the code instantiating localforage runs, it should alleviate the problem.

wow, thanks @sherl0cks.
This solution works for me.

[julianCast]

@beshkenadze

@waleedarshad you have to disable a persist reducer for the server-side rendering, something like that:

Hi! Does this mean is an issue between localforage and SSR? Can you expand ?

The only way I can reproduce this is by blocking site data storing from the browser, but seeing so many issues I don't think that many users disabled it. Is there another reason this could be happening? Thank you!

[wangmeijian]

The error is still valid for window chrome V123.0.6312.59(64bit) :(