-
Notifications
You must be signed in to change notification settings - Fork 875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexedDB exception on Firestore batch.commit with latest Firebase SDK 9.6.10 #6110
Comments
@olivierkrener Thank you for reporting. I will try to figure out where this is going on. |
I have a strong suspicion what is causing this, but I cannot create a repro. I was wondering if it was possible to see the keys of the documents your are mutating? You can also send me the list offline (mrschmidtgoogle.com). Since I have an idea for a fix, I do not necessarily need the smallest possible repo case. |
@schmidt-sebastian Most of these keys are autogenerated by Firestore when doing a set operation but two are custom keys: |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
After upgrading from v9.6.9 to v9.6.10 with persistence enabled, some writes result in the following IndexedDB exception:
And the writes are not propagated to the backend.
Rolling back to v9.6.9 solves the issue.
I would guess this issue is due to the modifications on the IndexedDB data type coming with v9.6.10 as mentioned in the release notes:
Note that the issue also occurs in incognito mode so it should not be due to any pre-existing data in IndexedDB or migration issue.
I cannot give a simple reproduction as the case when the write fails is a fairly complex batch operation with multiple writes (delete, set, update) and I have not tested thoroughly v9.6.10 to see if there are simpler cases leading to the same issue. But it is deterministic, in my app I can reproduce it 100% of the time, doing one specific action.
The text was updated successfully, but these errors were encountered: