-
Notifications
You must be signed in to change notification settings - Fork 927
Firefox Private Browsing: A mutation operation was attempted on a database that did not allow mutations #4069
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Triage note: This seems to be in auth code accessing indexedDB. |
I'm getting the same issue in Firebox 82.0.3 Private Browsing with Firebase SDK version 8.0.2 on Windows 10. |
Is the error raised from here? @hsubox76 |
Worth mentioning that this seems to be a fatal error. There doesn't seem to be a way to catch errors when calling I guess the only workaround is to wrap any firebase.auth calls in a timeout since there's a chance it'll hit a silent dead end. |
Is someone find a solution to |
@aliokan in my own project at least, this bug only appears in very recent versions. If you step back through the availalbe versions until the bug goes away, you should be able to mitigate it for the the time being. |
This bug appeared in 8.0.2 release https://firebase.google.com/support/release-notes/js#version_802_-_november_12_2020 |
I think this may be the same bug as #4113. I believe Firefox's message for that same error ("IDBFactory.open() called in an invalid security context") is the text reported in this issue ("A mutation operation was attempted on a database that did not allow mutations.") |
Hi everyone, thanks for your patience. This should be fixed by #4146, which is included in |
Steps to reproduce:
When opening the website with Firefox private browsing the following error is thrown:
Uncaught Error: InvalidStateError: A mutation operation was attempted on a database that did not allow mutations.
This is thrown here:
The text was updated successfully, but these errors were encountered: