IndexedDB instance on Web is not persisted

[felangel]

Steps to Reproduce
See felangel/bloc#4335 for detailed reproduction steps.

I believe this is because the underlying IndexedDB instance is not configure to be persistent.

You can see a sample at https://flutter-firebase-auth-2b1c3.web.app.

Version

• Platform: Web
• Flutter version: 3.27.3
• Hive version: 2.9.0

[Rexios80]

The counter persists for me on that sample in both Safari and Chrome. Am I supposed to be seeing something different?

[felangel]

The counter persists for me on that sample in both Safari and Chrome. Am I supposed to be seeing something different?

It's an issue when adding packages and re-deploying (then the cached state is lost) but I think it has something to do with the default Flutter service worker. I added more context in the linked bloc issue. When I disabled the service worker (flutter build web --pwa-strategy=none) I was no longer able to reproduce the issue so I think we can close this 🤷

In general though it might be nice to document how hive_ce will handle persistence on web (what the durability is and whether the database will be guaranteed to be persisted or not). It seems like the database is not guaranteed to be persisted and as a result it's probably not suitable for cases when the application relies on stored data being there in subsequent loads.

[Rexios80]

I think that "Is persistent" field is related to this: https://developer.mozilla.org/en-US/docs/Web/API/StorageManager/persist

Maybe I could try enabling it in hive?

Web data in general is not guaranteed to persist

[Rexios80]

Try this code and see if anything changes: #74

I can't get persistence to enable on localhost, but maybe it works on a deployed site