Chrome switching between asyncStorage and webSQLStorage on page reload

[MatthewAlner]

version: "@ionic/storage": "^2.2.0"
chrome version: 83.0.4103.116 (Official Build) (64-bit)

On first page load it uses asyncStorage then on a hard refresh or if I make a code change and it reloads, it swaps to using webSQLStorage. This doesn't happen in Safari or Firefox as far as I can tell.

I have worked around the issue by specifying my drivers an omitting websql

    IonicStorageModule.forRoot({
      driverOrder: ['indexeddb', 'sqlite'],
    }),

before I didn't pass anything, IonicStorageModule.forRoot()

Here is a video of the issue

https://youtu.be/CZN_cTlPd6U

Cheers,

Matt

[lincolnthree]

Also having this issue. It's super strange.

[lincolnthree]

Seems to be related to indexeddb not being ready:

When indexeddb is the only driver selected:

driverOrder: ['indexeddb']

rror: No available storage method found.
Error: No available storage method found.
    at :8100/vendor.js:56260:25 [angular]
    at Object.onInvoke (vendor.js:113715) [angular]
    at :8100/polyfills.js:7361:40 [angular]
    at Object.onInvokeTask (vendor.js:113703) [angular]
    at drainMicroTaskQueue (zone.js:583) [<root>]
    at resolvePromise (zone.js:1215) [angular]
    at resolvePromise (zone.js:1165) [angular]
    at :8100/polyfills.js:7364:21 [angular]
    at Object.onInvokeTask (vendor.js:113703) [angular]
    at drainMicroTaskQueue (zone.js:583) [<root>]

[lincolnthree]

I believe this is the cause. LocalForage does not seem to detect Chrome's indexedDb reliably:

localForage/localForage#999

Worse yet, @ionic/storage (or NPM) forces an dependency version of localForage that needs to be overridden to patch this.

[mlynch]

v3 which will be out in a few weeks uses the latest of localForage so going to close this

[lincolnthree]

@mlynch I do not believe my PR with the fix was merged into localForage. This issue should probably not be closed.

To be honest, the localForage project seems mostly dead/unmaintained now. You might consider forking it or switching to something else.

[mlynch]

Strange, I'm looking at your PR and it's essentially doing the same thing as the code that is already there. the idb isn't a chrome global, it's coming from the import in utils/idb.js which is pulling window.indexedDB. I would be shocked if window.indexedDB isn't available immediately as the script runs 🤔

Will keep an eye on it though, thanks for the info.

[lincolnthree]

@mlynch I'd be lying if I said I fully understand how browsers are providing IDB. And, honestly, the loss of WEBSQL is a real disappointment. The number of inconsistently reproducible IDB bugs (particularly with Safari) is stunning.

[sebaferreras]

@lincolnthree I think I'm experiencing the same issue... were you able to find a workaround or at least more information about why it happens? Thanks :)

[lincolnthree]

My workaround was to fork localForage, use the PR I submitted, and force everything to use my version -- since the project seems not to be maintained any longer. It seems there may be a better solution, but I haven't tried it, since what I have works and I don't want to mess with it and risk breaking things :)