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
{{ message }}
This repository has been archived by the owner on Aug 9, 2021. It is now read-only.
Describe the bug
I created a space in one browser, then I logged in using another browser and tried to access that space. I got the following error:
"OpenError: A mutation operation was attempted on a database that did not allow mutations"
It's worth noting that the space.syncDone promise never resolves. @oed said this might be a bug, but I haven't had a chance to open its own dedicated issue.
Another note: this could be caused by trying to access a space from a private browser, maybe?
To Reproduce
Steps to reproduce the behavior:
Open Box with Ethereum account
Open space
Store some data to said space
Use a private browser and Open Box with same Ethereum account.
Try to open the same space, error should be thrown.
Expected behavior
A user should be able to sign in and access a space from any browser or device.
Desktop (please complete the following information):
OS: [e.g. iOS]: MacOS 10.14.6
Browser [e.g. chrome, safari] Firefox 69.0.1
The text was updated successfully, but these errors were encountered:
Hey @jehunter5811 thanks for reporting! Can you provide some more information? In particular I'm wondering what wallet your are using. Is this using MetaMask in firefox or something different?
@jehunter5811 it shouldn't be a problem as long as it conforms to the standard ethereum rpc-provider api.
It could have something to do with permissions in the private tab and localstorage/indexedDB perhaps though.
Seeing this issue too on Firefox when calling Box.openBox(). Brave with shields enabled doesn't seem to work either so it might be a cross-site storage issue.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I created a space in one browser, then I logged in using another browser and tried to access that space. I got the following error:
"OpenError: A mutation operation was attempted on a database that did not allow mutations"
It's worth noting that the space.syncDone promise never resolves. @oed said this might be a bug, but I haven't had a chance to open its own dedicated issue.
Another note: this could be caused by trying to access a space from a private browser, maybe?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A user should be able to sign in and access a space from any browser or device.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: