-
Notifications
You must be signed in to change notification settings - Fork 65
Should not throw "Key not found in database" exception #891
Comments
@dkent600 if switching between versions you may see this error, i would try clearing browser storage for your application and trying 1.21.0 again, but let me if you see it more regularly |
Having to clear browser storage would be an issue for our users. |
yes of course, just saying if going between versions in development you may be more likely to see this is version 1.20.x already deployed to your users? |
actually, now that you mention it, our 1.20.* code hasn't gone out yet.... |
@zachferland I installed 1.21 and cleaned everything out and now in
|
@dkent600 have not been able to replicate yet, what browser do you see this in? and can you run 'npm list levelup level-js orbit-db-storage-adapter' to see what versions of these dependencies you have? |
Browser: Edge Chromium
|
@zachferland Any updates on this? Thanks. |
During this:
(or was it in
auth
, sorry I don't recall)an exception is thrown:
spaceName
is "DAOstack"Using [email protected]
The web3provider is pointing at rinkeby.
The text was updated successfully, but these errors were encountered: