AsyncQueue is already failed: The transaction was aborted, so the request cannot be fulfilled.
Problem
Describe your environment Operating System version: Android, so the version varies Browser version: Usually latest Chrome (73.0.3683.90) Firebase SDK version: 5.9.3 Firebase Product: Firestore Describe the problem We're seeing the following error more and more lately (via our error reporting service): [code block] This error is of a critical nature, as it entirely breaks the DB layer. ~~Data stops getting written to the database, and it can be somewhat difficult to detect when the DB gets into this state, as the error is only thrown once. You can then call all the DB functions, and everything appears to work as normal, except no data ends up in the cloud (nor the persistence layer).~~ (This was incorrect. Our error collection service just aggregated the data) Steps to reproduce: Apologies, but it's entirely periodic. It could be related to IndexedDB reaching a certain size, as clearing it out seems to postpone the problem for a few weeks. I have no theories as to what causes the "transaction to be aborted". We were hoping the new garbage collection feature would take care of the problem, but so far it doesn't seem like it. The devices running this are of the model "Samsung T580". Any other info you need, let me know.
Error Output
error more and more lately (via our error reporting service):
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: AsyncQueue is already failed: The transaction was aborted, so the request cannot be fulfilled.
@larssn Thanks for the report and sorry you're running into issues. You said that clearing IndexedDB seems to postpone the problem and so you think it's size-related. Does that mean that just refreshing the browser (_without_ clearing IndexedDB) does not help? Once the error happens, the problem continues to happen until you clear IndexedDB persistence? If so, that would definitely indicate th
Trust Score
1 verification
- 1
@larssn Thanks for the report and sorry you're running into issues.
@larssn Thanks for the report and sorry you're running into issues.
- 2
You said that clearing IndexedDB seems to postpone the problem and so you think
You said that clearing IndexedDB seems to postpone the problem and so you think it's size-related. Does that mean that just refreshing the browser (_without_ clearing IndexedDB) does not help? Once the error happens, the problem continues to happen until you clear IndexedDB persistence? If so, that would definitely indicate this is a size issue. But I want to be clear. Thanks!
Validation
Resolved in firebase/firebase-js-sdk GitHub issue #1642. Community reactions: 0 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep