Storage not persisting on Chrome and Firefox
See original GitHub issueApparently there’s an error: DOMException: "The operation failed because the requested database object could not be found. For example, an object store did not exist but was being opened."
Gonna figure this out on Monday.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Browser.storage.local is not persistent - Mozilla Discourse
As long as you are using browser.storage.local.set() to save items to the storage, it should be persistent. If you are loading it as...
Read more >How can I fix the local storage issue in my browser? - Hipporello
If the problem persists: · Click on the three dots icon at the top right. · Click "Settings". · Click "Advanced". · Select...
Read more >Persistent local storage for both Firefox and Chrome?
You can store far more than 50 MB in IndexedDB in both Firefox and Chrome, assuming the user has enough hard drive space....
Read more >Local Storage not showing data : r/firefox - Reddit
Firefox Developer Tools : Storage : Local Storage is unpopulated but a console.log(localStorage); proves the code is working. Like upthepowerx ...
Read more >How-to: View Local Storage in Chrome and Firefox - UI Vision
And as the same suggests, all is saved locally on the machine where the browser is installed. Local storage is not in the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Are you sure Chrome isn’t persisting storage? It uses the filesystem API instead if IDB for persistence. It’d likely error out if it had trouble writing stuff, too.
I’m not sure how we can handle deleting parts of IndexedDB, I think the storage layer has a particular way of interacting with it, so there should probably be an API for deletion there instead of deleting it externally.
Does fully deleting IDB and refreshing the page help?
Repro: From a new
create-react-app
:yarn add dat-sdk
App.js
p2p.js
Works initially in the browser loading an image, however, after you delete either the Dat folder or IDBMutableFile inside the Indexed DB tab of Firefox it will either fail silently or give the DOMException.