Firebase-js-sdk: CRITICAL : Error · FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Trying to deserialize version that isn't set

Created on 27 Oct 2018 · 34Comments · Source: firebase/firebase-js-sdk

[REQUIRED] Describe your environment

Operating System version: iOS 11 and iOS 12
Firebase SDK version: latest (5.5.6) & 5.5.0
Firebase Product: Firestore

Describe the problem

We have hundreds of users that cannot even use the app because we have this error.

Steps to reproduce:

Only open a couple of snapshot... Then this error is popping in console and no get(), set() or update() is working after that.

Relevant Code:

There is no code I can show you to reproduce that, it seems to be an internal library error and we just need to know why this is happening. Just knowing the reason this error is raised could help us find the problem. Thanks

firestore

Source

sambegin

👍5

Most helpful comment

The rollback is now complete, folks. We do expect this to have fixed the issue, so please let us know if it reoccurs!

wsh on 31 Oct 2018

👍3

All 34 comments

You're going to need to give us some more data. Yes this is an internal error, but it's an assertion failure indicating that an assumption didn't hold. The assertion failure is happening in a routine that's used to deserialize messages from the server or the local store so it really could be anything triggering this.

So, please help us help you:

Do you have persistence enabled? Multi-tab?
Is this happening on specific browsers? You write that this is happening on iOS11 and iOS12--are you seeing this on any desktop browsers?

Even if you don't have specific code that does this trying to come up with a series of actions that reproduces this will help.

wilhuff on 27 Oct 2018

We have persistence enabled.
We have multi-tab enabled. ({ experimentalTabSynchronization: true }). This error occurred with version 5.5.0 and 5.5.6 now.

Looking at our logs right now it seems to only happen on iOS devices (we have a cordova app so same code is used between android and iOS users, but 95 % of our users are on iOS)

We did not see this on browsers because most of our users is on mobile devices so I don't know if multitab flag is in play in this case. If you need anything else let me know

sambegin on 27 Oct 2018

If you've observed this yourself a run with logging enabled would be helpful: https://firebase.google.com/docs/reference/js/firebase.firestore.Firestore#setLogLevel

Was this working for you prior to 5.5.0? If you downgrade does the problem go away?

Basically anything you can do to help narrow this down would be helpful.

We're not Cordova experts, so even if you can't reproduce this reliably, sharing a project that does occasionally reproduce the issue would make this much easier for us to figure out.

wilhuff on 29 Oct 2018

I'm facing the same issue as well. Unfortunately unable to reproduce it but I'm seeing it in the field.

sengoontoh on 30 Oct 2018

👍3

When you say you’re seeing this as well, is it the identical circumstances, or are you seeing this in non-Cordova settings?

wilhuff on 30 Oct 2018

I can't speak for sengoontoh but we are experiencing this issue on Cordova iOS and Safari iOS at the moment.

Here is a StackTrace from Mobile Safari 11.4.1

screenshot_2018-10-29 medyx timeline 1

jggc on 30 Oct 2018

I'm facing the same issue as well. Unfortunately unable to reproduce it but I'm seeing it in the field.

I'm seeing it on Cordova ios 11.4.1, 12.0, and 12.0.1 as well as Cordova android 8.0.

It seems to happen when the app is first launched.

sengoontoh on 30 Oct 2018

We are effectively receiving this error
FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Got result for empty write pipeline
along with with the error in this issue

sambegin on 30 Oct 2018

We're also seeing this on production now, it affects also desktop browsers, atleast chrome and safari. Latest error was sent from (according to sentry.io)

Chrome, Version: 69.0.3497
Mac OS X, Version: 10.13.6

To my eyes the stack is completely useless, but I may be wrong:

Unhandled Promise rejection: FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Trying to deserialize version that isn't set ; Zone: <root> ; Task: Promise.then ; Value: Error: FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Trying to deserialize version that isn't set Error: FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Trying to deserialize version that isn't set
at fail (https://tool.sitysite.com/main.b0901a2e8718ac755364.js:148689:11)
at assert (https://tool.sitysite.com/main.b0901a2e8718ac755364.js:148697:9)
at JsonProtoSerializer.push../node_modules/@firebase/firestore/dist/index.cjs.js.JsonProtoSerializer.fromVersion (https://tool.sitysite.com/main.b0901a2e8718ac755364.js:154232:9)
at PersistentWriteStream.push../node_modules/@firebase/firestore/dist/index.cjs.js.PersistentWriteStream.onMessage (https://tool.sitysite.com/main.b0901a2e8718ac755364.js:162883:49)
at https://tool.sitysite.com/main.b0901a2e8718ac755364.js:162713:30
at https://tool.sitysite.com/main.b0901a2e8718ac755364.js:162755:28
at https://tool.sitysite.com/main.b0901a2e8718ac755364.js:156243:20
at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8009:30)
at Object.onInvoke (https://tool.sitysite.com/main.b0901a2e8718ac755364.js:70702:33)
at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invoke (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8008:36)
at Zone.push../node_modules/zone.js/dist/zone.js.Zone.run (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:7753:47)
at https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8492:38
at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8042:35)
at Object.onInvokeTask (https://tool.sitysite.com/main.b0901a2e8718ac755364.js:70693:33)
at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8041:40)
at Zone.push../node_modules/zone.js/dist/zone.js.Zone.runTask (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:7809:51)
at drainMicroTaskQueue (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8216:39)
at ZoneTask.push../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask [as invoke] (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:8121:25)
at invokeTask (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:9160:18)
at XMLHttpRequest.globalZoneAwareCallback (https://tool.sitysite.com/polyfills.44708cf62dd1377ea157.js:9186:21)

is there something more that I can provide @wilhuff ? It seems that it's happening for us when saving rather complex object to firestore, but other than that it's really guess work. Maybe time to make the thing easier to debug?

swftvsn on 30 Oct 2018

And it's occurring only for handful of users, quite low percentage for us, so I've not been able to repro yet.

swftvsn on 30 Oct 2018

Are yall seeing these errors as well?

FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Got result for empty write pipeline

sengoontoh on 30 Oct 2018

@sengoontoh Yes for us. We have about 35 % "pipeline" errors and 65% "deserialize" errors

sambegin on 30 Oct 2018

Just to follow up for those that aren't working with our support org: this is a Firestore-wide incident: https://status.firebase.google.com/incident/Cloud%20Firestore/18008.

All versions of the JS SDK are affected. We're in the process of rolling back the backend release that that introduced the issue.

wilhuff on 30 Oct 2018

🎉3

Rollback is complete.

@sambegin, @sengoontoh, @jggc, @swftvsn could you confirm that you're no longer seeing issues?

wilhuff on 30 Oct 2018

@wilhuff

Our users doesn't use the app very much at this time of the day so I'll be able to confirm it later today
or tomorrow. I've not seen the error since about more than an hour ago in our logs.

sambegin on 30 Oct 2018

@wilhuff

I just saw an error at 3:39:43.088 PM PST

FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Got result for empty write pipeline

sengoontoh on 30 Oct 2018

@wilhuff

Got a FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: Trying to deserialize version that isn't set

at 3:52 pm PST

sengoontoh on 31 Oct 2018

@wilhuff

Another deserialize INTERNAL ASSERTION FAILED at 4:12 pm PST.

sengoontoh on 31 Oct 2018

Hi all--mea culpa. We're still doing the rollback, I ran a query incorrectly and jumped the gun. We expect this to complete within the hour, and I'll let you know when it has.

wsh on 31 Oct 2018

Sigh. It turns out the rollback was only mostly complete. We’ll keep you posted.

wilhuff on 31 Oct 2018

Appreciate the gargantuan effort folks!

sengoontoh on 31 Oct 2018

❤1

The rollback is now complete, folks. We do expect this to have fixed the issue, so please let us know if it reoccurs!

wsh on 31 Oct 2018

👍3

Last occurence of this error at 4:17pm EST yesterday, almot 14 hours ago. But usage of our app is lower outside business hours so i'd wait 24h more before calling it over.

jggc on 31 Oct 2018

I'm still seeing these errors as of 3 AM PST today.

sengoontoh on 31 Oct 2018

@sengoontoh did you see any decrease in occurence since the rollback completed?

jggc on 31 Oct 2018

Doesn't feel like it. It's also really early right now though so most of my users are not on yet.

sengoontoh on 31 Oct 2018

I'm still seeing these errors trickle in. One in the past hour. @sambegin, @jggc, @swftvsn are you still seeing it?

sengoontoh on 31 Oct 2018

@sengoontoh Not on our side, the last one we've seen was 21h ago.

sambegin on 31 Oct 2018

@sengoontoh With the exception of your reports, all the data we have shows that this issue has been resolved. Is it possible that the error reports you're seeing happened previously and are just trickling in now as devices reconnect?

wilhuff on 31 Oct 2018

No errors here since the rollback.

swftvsn on 1 Nov 2018

My application has persistence enabled, but only on single tab.
The error continued to appear today using a browser with data stored locally.
With Incognito window everything worked fine.

To fix the problem everywhere I have done:
In Chrome > Developer Tools > Application > delete the IndexedDB

yankedev on 16 Dec 2018

@yankedev Can you confirm exactly what error you were seeing? Thanks.

mikelehen on 16 Dec 2018

The original issue was resolved quite a while ago. If anybody is still getting errors, please open a new issue with full details / repro steps.

mikelehen on 19 Jan 2019

I got the same error when I tried to sign in via google firebase, which is 5.5.6 but error message is

Error: FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: Internal error opening backing store for indexedDB.open.
auth.service.ts:96
ERROR
core.js:1673
Error: Uncaught (in promise): Error: FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: Internal error opening backing store for indexedDB.open.
core.js:1673
[2019-02-09T17:09:42.258Z] @firebase/firestore: Firestore (5.5.0): FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: Internal error opening backing store for indexedDB.open.
index.esm.js:77
message:"FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: Internal error opening backing store for indexedDB.open."
stack:"Error: FIRESTORE (5.5.0) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: Internal error opening backing store for indexedDB.open.