You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every other client SDK (iOS, Android and Flutter) supports persisting data offline with the Realtime Database and so this statement in the documentation holds true.
However, the web with the JavaScript SDK has been left behind and swept under the rug:
it only supports persisting writes offline by keeping them stored in memory. If the process is closed or the browser reloads everything is gone.
reads are not cached at all, not in memory nor on disk. If you go offline, an onValue() that has been invoked before will not run. If you start offline, it's the same result.
I know the Realtime Database is not new and shiny like the FireStore but it should support these use cases and get parity with other SDKs so that the docs hold true.
Steps and code to reproduce issue
Run an onValue() offline or do a set() whilst offline after reloading your browser.
The text was updated successfully, but these errors were encountered:
I'm experiencing the same issue: using persistentLocalCache on web, the indexedDB will store mutations on existing data items (update and delete)--if you close and reopen a browser it will sync with firestore. However addDoc or setDoc do not appear in the IndexedDB, thus after closing the browser/PWA while offline, the new data is lost.
Operating System
Any
Browser Version
Any
Firebase SDK Version
Any
Firebase SDK Product:
Database
Describe your project's tooling
N/A
Describe the problem
Every other client SDK (iOS, Android and Flutter) supports persisting data offline with the Realtime Database and so this statement in the documentation holds true.
However, the web with the JavaScript SDK has been left behind and swept under the rug:
I know the Realtime Database is not new and shiny like the FireStore but it should support these use cases and get parity with other SDKs so that the docs hold true.
Steps and code to reproduce issue
Run an onValue() offline or do a set() whilst offline after reloading your browser.
The text was updated successfully, but these errors were encountered: