FIRESTORE (10.9.0) INTERNAL ASSERTION FAILED: Unexpected state

[kmorgan8588]

Operating System

Windows 10

Browser Version

Chrome 124

Firebase SDK Version

10.9.0

Firebase SDK Product:

Firestore

Describe your project's tooling

React application with Webpack

Describe the problem

Customer using our application in production attempted to update a document, and it failed with this error. We were able to parse the error stack seen below. Looks like the async_queue has already failed?

Stack trace:

../node_modules/.pnpm/@firebase+firestore@4.5.0_@firebase+app@0.9.29/node_modules/@firebase/firestore/src/util/assert.ts:40:8:null
../node_modules/.pnpm/@firebase+firestore@4.5.0_@firebase+app@0.9.29/node_modules/@firebase/firestore/src/util/async_queue_impl.ts:238:6:fail
../node_modules/.pnpm/@firebase+firestore@4.5.0_@firebase+app@0.9.29/node_modules/@firebase/firestore/src/util/async_queue_impl.ts:119:9:lu
../node_modules/.pnpm/@firebase+firestore@4.5.0_@firebase+app@0.9.29/node_modules/@firebase/firestore/src/util/async_queue_impl.ts:93:9:enqueue
../node_modules/.pnpm/@firebase+firestore@4.5.0_@firebase+app@0.9.29/node_modules/@firebase/firestore/src/util/async_queue.ts:193:20:enqueueAndForget
../node_modules/.pnpm/@firebase+firestore@4.5.0_@firebase+app@0.9.29/node_modules/@firebase/firestore/src/util/async_queue.ts:160:45:handleDelayElapsed

Steps and code to reproduce issue

Steps to reproduce: Unknown, we've seen these internal assertions occur in the past, but it's intermittent and not consistent to reproduce

[cherylEnkidu]

Hi,

If you run into this issue when you develop locally. Could you please enable the debug log for us to get more info of this failure?

Also, could you please try to downgrade your SDK version to 10.6.0 to see if that fix your problem?

[michaelAtCoalesce]

@cherylEnkidu - kyle and i are working on this together so i am responding on his behalf.

we cannot turn on debug logging for this, as we do not see it locally, and we do not have a recreate case. it happens very intermittently in production with customers (thus why we cannot turn on logging)

we are happy to try custom builds with specific logging for this issue if needed (maybe you can add some telemetry or logs right before the offending assert fires?)- but turning on all debug logging is a no-go for us.

[cherylEnkidu]

Hi @michaelAtCoalesce ,

Thank you for the reply! Have you tried to downgrade the SDK version to 10.6.0? This version hasn't received any connectivity issue reports yet.

[google-oss-bot]

Hey @kmorgan8588. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[michaelAtCoalesce]

@cherylEnkidu we cannot downgrade at this time...