[Error] InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.

[AugustinGrigorov]

[REQUIRED] Describe your environment

• Operating System version: iOS Version:13.3.1
• Browser version: Mobile Safari Version:13.0.5
• Firebase SDK version: 7.9.1
• Firebase Product: firestore

[REQUIRED] Describe the problem

Steps to reproduce:

I can't reliably reproduce it so not entirely sure what specifically causes it but here is the Sentry error:
https://sentry.io/share/issue/03f7cacb9f394cdd9867f13ad40345d8/
Once this errors subsequent requests start failing like this:
https://sentry.io/share/issue/aab1ab9ce88e4d50a3e40edbc27c0700/

Relevant Code:

This is my firebase setup:
https://github.com/AugustinGrigorov/vocabulary-builder/blob/master/src/utils/firebase.js

[schmidt-sebastian]

@AugustinGrigorov Sorry to hear about your troubles!

It looks like you are experiencing something akin to #1533. The good news is that you are not on your own, the bad news is that this seems to be a longstanding issue that is caused by unexpected behavior in Mobile Safari that we haven't been able to completely work around.

We are currently discussing how to make our SDK more tolerant to IndexedDb failures, which would address this issue, as well as #1533 and #2581. We already retry IndexedDb writes up to five times, but this doesn't seem to help in some scenarios (e.g. when the app is not in the foreground).

[AugustinGrigorov]

Thanks! That makes sense. Cross-browser issues can be annoying.

[aidanas]

We are also experiencing similar issue. On lates version - 7.17.1
Unfortunately, I was not able to recreate it on an isolated hello world but it happens frequently on our production app with following steps/setup.
We use persistence enabled Firestore. Our app is Cordova based multi page app. Between navigations we call firebase destroy and only then change the href. Firebase is then reinitialised on a next screen app on the next screen. The problem happens when users navigate around a bit, usually about 3 screen. Then put app to background. Disable and re-enable wifi. Then bring app to foreground.
At that point we get errors in logs:

  @firebase/firestore: – "Firestore (7.17.1): INTERNAL UNHANDLED ERROR: " (1)
Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.
Unhandled Promise Rejection: InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.
 @firebase/firestore: – "Firestore (7.17.1): FIRESTORE (7.17.1) INTERNAL ASSERTION FAILED: Unexpected state"

[veeralpatel]

+1 -- seems to be happening most on Mobile Safari

[luisfelipesd]

this is affecting all of our users for the registering process. any update?

[zeari]

this is affecting all of our users for the registering process. any update?

same here 🤕

[aToO57]

Same here :(

[schmidt-sebastian]

Can one of you provide the logs that immediately proceed these failures? This will help me narrow down what transaction is failing. Furthermore, do you see more or fewer of these errors since 7.18? 7.18 is the first version that is meant to address these issues.

FYI Iam on vacation next week but will pick up this work once I get back.

[olearycrew]

Is anyone aware of a workaround for users?

[Aquahugs]

Yep still having this problem as well :( really effecting user growth for a project im currently launching

[IvanDeluxe]

Unfortunately, I have no logs to share, but we have a stocktaking app in which you count items in stock by adding them to the current count. This means that during a single inventory count user repeatedly adds items to count.

There's a user that's on iOS 13.16.1 (Firebase version 7.19 currently) and she usually has to reload the app after adding 10 or 20 items (that's 10 or 20 writes) because she experiences true data loss.

We've set a .catch((e)=>{...}) that disables the button in question if something goes wrong, but in this case nothing happens - she probably gets an error in the console, but that is currently beyond our powers :)

I've tested the "catch" by calling firebase.firestore().terminate() disabling persistence + setting Network to Offline and it works as expected, but in her case, she can continue using the app, there's just no data being added / removed :(