-
Notifications
You must be signed in to change notification settings - Fork 894
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
Messaging in Firefox private mode (IndexedDb) #5868
Comments
I don't think messaging is supposed to work in private mode? It definitely doesn't work in incognito on Chrome. |
Drive-by comment: We had the same issue in Firestore: #5377. Firefox private browsing does not (currently) support IndexedDb and Firefox has an open feature request to address this: https://bugzilla.mozilla.org/show_bug.cgi?id=1639542. You can configure Firefox to allow IndexedDb in private browsing mode to confirm that IndexedDb is indeed the root cause: #5377 (comment). Obviously, this isn't really a viable solution for your users though, just a means of confirming the root cause. |
I'd just like to say that I am seeing the same error using Firebase 9.6.4. I'm using Firebase in an Angular app which fails to load in Firefox private browsing mode when importing the messaging module. I can confirm that enabling DB persistence in Firefox private browsing mode does resolve the error. But yeah, obviously not viable. |
Messaging is not supported in environments that don't allow indexedDB. In order to prevent the app crashing if it's run in one of those environments, you can use the |
@hsubox76 Calling I checked the v9 compat version meanwhile, there the code doesn't use a Promise and that's why that version works. But I need to use the modular version for other reasons. |
I see, the compat code actually is missing this check and that's incorrect, but the modular code should be wrapping the await in a try/catch so that's also incorrect. Thanks for bringing this up, will look into fixing both. |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
We recently upgraded our Angular app to Firebase v9 Modular. After some DNS changes we tested our app with Tor and were presented with a white page. We then reproduced the issue with Firefox private mode. Normal Firefox sessions work. When allowing browser history in Firefox private mode, it also works.
When using the private mode, we see the following error:
Unhandled Promise rejection: A mutation operation was attempted on a database that did not allow mutations. ; Zone: <root> ; Task: Promise.then ; Value: A mutation operation was attempted on a database that did not allow mutations.
I tried disabling IndexedDb then for the whole app, but the problem lies within in the initialization of the messaging module.
Steps to reproduce:
Any app using AngularFire with the messaging module should be affected: https://github.com/angular/angularfire
The text was updated successfully, but these errors were encountered: