INTERNAL ASSERTION FAILED: Unexpected state, occurs in Browser

[michaelAtCoalesce]

• Operating System version:N/A
• Browser version: Firefox
• Firebase SDK version: "firebase": "^9.17.1",

Steps to reproduce:

Reproduction is unclear, customer had a browser tab open for awhile, Wasn't doing anything actively when it happened.

Error: Error: FIRESTORE (9.12.1) INTERNAL ASSERTION FAILED: Unexpected state STACK: ../../../node_modules/@firebase/firestore/dist/index.esm2017.js:(k:139 
../../../node_modules/@firebase/firestore/dist/index.esm2017.js:(value:17048 
../../../node_modules/@firebase/firestore/dist/index.esm2017.js:(enqueueAndForgetEvenWhileRestricted:16963 
../../../node_modules/@firebase/firestore/dist/index.esm2017.js:(Wc:16947 
../../../node_modules/@firebase/firestore/dist/index.esm2017

[google-oss-bot]

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

[milaGGL]

Hi @michaelAtCoalesce, thank you for reporting this issue.

Since it is hard to repro, we might have to reply on debug log to provide us with some insights. Could you please enable logging with firebase.firestore.setLogLevel('debug') , and have one of your users capture the log output from the console when they notice this error? Please make sure you have redacted any sensitive information from the log before sharing it here.

Also, would it be possible to check if this problem is only happening with Firefox?

[dconeybe]

[possible relevant context] This issue arose from discussing #6931 with the OP.

[milaGGL]

• Firebase SDK version: "firebase": "^9.17.1",

One thing tho, the Firestore version in the error message is 9.12.1, different from the firebase version that you mentioned. It might worth checking out.

[michaelAtCoalesce]

thanks @milaGGL - i would definitely trust the number coming from the log message ;)

one question about the debug log level` - is this something that could be turned on all the time? we dont have a good recreatable test case, so we'd have to crank the debug logging level up all the time in order to capture it the next time it happens. looking at our logs, it happens a handful of times a week.

alternatively, we are happy to accept a patched version with appropriate logs, or updating to a version of firestore with more targeted telemetry for when this happens.

we definitely would like to work with you however possible to get logs to rectify this issue.

[milaGGL]

@michaelAtCoalesce, yes, you can enable debug-level logging for the Firestore JavaScript SDK all the time, but this might generate a large amount of log output, so it is better to disable it once we locate the root cause of the error.

Taking one step further, the stack trace indicate that the exception is occurring during a call to enqueueAndForgetEvenWhileRestricted(), a method that is called in exactly 2 places: terminate() and clearIndexedDbPersistence(). Are these functions called in your app?

If yes, I would suggest enable debug logging before each of these method calls and disable it after awaiting the promise that they return, to reduce the log output volume. Something like this:

setLogLevel('debug');
await terminate(db);
setLogLevel('silent');

Regarding the terminate() function, are you running terminate() in response to the user closing the web page or navigating away? It is possible that the call to terminate() is getting interrupted by the web page being unloaded.