I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Thanks for the detailed report. I'm not able to reproduce it on Safari 16.1. This is the sample app I am using (compat app and auth):

import firebase from "firebase/compat/app";
import 'firebase/compat/auth';

firebase.initializeApp(/** my config **/);
firebase.auth().onAuthStateChanged(user => console.log('user', user ? user.uid : 'no user'));

firebase.auth().signInAnonymously();

I also tried with modular, and wasn't able to reproduce it either.

Is there anything I should add to the code to trigger the error, or is there anything special about the Safari environment (iframe, privacy settings)?

Is there a firebase-heartbeat-database in the browser's indexedDB? (Can find it in the Storage tab of the Safari dev console). If so, does deleting it make the problem go away?

@hsubox76

• There is a firebase-heartbeat-database indexedDB, but it has no rows:
• I can't reproduce the issue when launched in a Safari Private Window. If that's the case, you would think that emptying the caches from a normal Window would fix the issue, but no... Develop -> Empty Caches doesn't resolve the issue.
• I can't reproduce it on https://fir-ui-demo-84a6c.firebaseapp.com
• The site where I am reproducing it, is: what.how. Perhaps you can try reproducing it there?

I think it might only occur when you have Crisp chat in your web app.

we have a bunch of reports of this issue.

@hsubox76 it doesn't seem to be a consistent issue though, users have reported that restarting Safari fixes the problem

in that case, it would be nice if firebase caught/exposed the issue somehow to the application? Just so that we can recover from it in a nicer fashion

Sure, I may be able to add a catch to

Do you think it would be all right to have it console.log the error if it catches it? I do want to make sure it's surfaced and not swallowed, but I don't want to clutter Sentry logs with console.error or console.warn. Is console.log ok? I think console.debug is too invisible (the user would have to deliberately turn debug logging on).

console.log is definitely fine, and even console.error could be good to be honest, since this could end up being somewhat fatal?

thanks for the fast response btw!