FIRESTORE (4.10.1) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: The requested version (1) is less than the existing version (2)

firebase/firestore: firestore 4.13 0 could not reach firestore backend
firebase 7.13 2
using maximum backoff delay to prevent overloading the backend
firestore offline first
firebase js sdk versions
firebase_database_emulator_host
firebase js sdk react native
firebase react version

I'm sorry for being vague, but I really don't know what to mention except that I am receiving this error! I have no idea why except that I think it has something to do with version in compatibility. Everything worked on one machine. I cloned it to another and have this error now.

I'm running Angular 5 with angularfire2.

Please let me know which logs, etc. would be helpful.

Thanks, Wayne

I am also using ngx-pwa-localStorage so it may have something to with: Chrome console error: The requested version (1) is less than the existing version (2)

below is my package.json

{
  "name": "scriptertainment",
  "version": "0.4.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular-devkit/core": "^0.4.6",
    "@angular-devkit/schematics": "0.0.52",
    "@angular/animations": "^5.0.0",
    "@angular/common": "^5.0.0",
    "@angular/compiler": "^5.0.0",
    "@angular/core": "^5.2.10",
    "@angular/forms": "^5.0.0",
    "@angular/http": "^5.0.0",
    "@angular/platform-browser": "^5.0.0",
    "@angular/platform-browser-dynamic": "^5.0.0",
    "@angular/router": "^5.0.0",
    "@angular/service-worker": "^5.2.10",
    "@ng-bootstrap/ng-bootstrap": "^1.1.0",
    "@ngx-pwa/local-storage": "^5.2.0",
    "angularfire2": "5.0.0-rc.6",
    "bootstrap": "4.0.0-beta.2",
    "core-js": "^2.4.1",
    "firebase": "^4.12.0",
    "ionicons": "^3.0.0",
    "ngx-filter-pipe": "2.1.0",
    "ngx-swiper-wrapper": "^5.3.8",
    "open-iconic": "^1.1.1",
    "pdfjs-dist": "^2.0.489",
    "rxjs": "^5.5.2",
    "swiper": "^4.2.0",
    "zone.js": "^0.8.14"
  },
  "devDependencies": {
    "@angular/cli": "^1.7.2",
    "@angular/compiler-cli": "^5.0.0",
    "@angular/language-service": "^5.0.0",
    "@types/jasmine": "~2.5.53",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~6.0.60",
    "codelyzer": "~3.2.0",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.1.2",
    "ts-node": "~3.2.0",
    "tslint": "~5.7.0",
    "typescript": "~2.4.2"
  }
}

Thanks to https://stackoverflow.com/users/819775/igor for the assistance.

The answer is to manually delete the firestore IndexDB entries. In Chrome, enter the Dev Console, go to application tab. Locate IndexDB on the left and expand. For each firebase db in the list, select the db and use the "Delete Database" button.

This was ok for me since my app is not yet in production, but I would have to imagine that for live sites, you'll need to implement a db delete call when the page loads and refresh the page or put in a place a temporary site redirect that handles the db cleanup.

Since the update seems to hose the FB DB, I'm not sure how you would reclaim that data. Hopefully, your app persists the data elsewhere, if it's important.

AsyncQueue is already failed: The transaction was aborted, so the , Describe your environment Operating System version: Android, so AsyncQueue is already failed: The transaction was aborted, so the request cannot be fulfilled. FIRESTORE (5.9.1) INTERNAL ASSERTION FAILED: AsyncQueue is have much less space free, then the storage quota could get smaller. 11 FIRESTORE (4.10.1) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: The requested version (1) is less than the existing version (2) Apr 23 '18 7 Swiper idangerous slider by items at view not one by one Feb 5 '17

I had the same issue when testing two different apps with two different versions of firebase.

The simplest solution I found was to just clear your browser history.

FIRESTORE (4.10.1) INTERNAL ASSERTION FAILED Error · Issue , We get this error when using the enablePersistence() method on the initialization of AngularFirestoreModule. Removing it makes it work as  Version 3.2.1 - July 26, 2016. Typescript 2.0 type definitions added to npm package. Authentication. Fixed issues with Safari private mode. More detailed debugging messages for internal errors. Version 3.2.0 - July 12, 2016 Storage. UploadTask can now be used like a Promise, and resolves with its snapshot data when the upload completes

I removed offline persistence and the error went away.

If you're not sure where that is, search codebase for variations of:

firebase.firestore().enablePersistence()

IINTERNAL ASSERTION FAILED: AsyncQueue is already failed , [REQUIRED] Describe your environment Operating System version: __ _ electron 7.1.2 Firebase SDK version: __7.6.1 Firebase Product: __ firestore (auth, In web browsers, multiple tabs share a single instance of IndexedDB, and the FIRESTORE (7.6.0) INTERNAL ASSERTION FAILED: AsyncQueue is already  Version 4.10.1 - March 9, 2018 Cloud Firestore Fixed a regression in the 4.10.0 Firebase iOS SDK release that prevented the SDK from communicating with the backend until successfully authenticating via Firebase Authentication or after unauthenticating and re-authenticating.

This error is caused when offline persistence is enabled and more than one tab is opened for the specific domain. Localhost also counts I find the error misleading though

Firestore: Attempt to get a record without an in-progress transaction , Hello, sorry if this is not a proper bug report, but I am out of ideas and Firebase SDK version: 6.0.2; Firebase Product: firestore (auth and storage also used) Several INTERNAL ASSERTION FAILED: AsyncQueue is already failed the iPad to turn the screen off; wait 1 minute (this seems to be required,  A/B Testing version 19.0.1. Internal changes to ensure functionality alignment with other SDK releases. App Indexing version 19.1.0. Internal changes to ensure functionality alignment with other SDK releases. Cloud Firestore version 21.4.0. Cloud Firestore previously required that every document read in a transaction must also be written. This

The issue is that the firebase cache setup in the browser cache is incompatible between some firebase versions. What worked best for me was to use an incognito browser window rather than clearing history.

Firebase JavaScript SDK Release Notes, As a result, the minimum supported NodeJS version is now 8.13.0 . The minified version of the Cloud Firestore library, added as an experimental option in library firebase-admin , which depends on @firebase/database , failed to compile. Fixed an issue with IndexedDb persistence that triggered an internal assert for  * Version bump for 4.8.1 Release Updated the version numbers of pods which are being released in 4.8.1 * Update from master Picking up a few last-minute changes to CHANGELOGs and tests for 4.8.1 release. * Update Core info for M21.1 Update missing version bump for M21.1 for FirebaseCore. * Remove over-aggressive assert.

User Wayne F. Kaskie, 11 FIRESTORE (4.10.1) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: The requested version (1) is less than the existing version (2) · 7 How to  Implement the first part of ArraySortedMap, which can insert, remove, and find entries. Does not include any of the iterator operations or views. #718 brings in the foundation of how those views wi

Error: FIRESTORE (4.5.0) INTERNAL ASSERTION FAILED, Error: FIRESTORE (4.5.0) INTERNAL ASSERTION FAILED: AsyncQueue is already failed: The transaction at fail (../node_modules/firebase/firestore/util/​assert.js:47:1) Now I just read in the group's description that the right place for bug Perhaps the IDBDatabase related ones may be consequence of  We could rework the code to make the assertion hold, but per offline discussion this assert doesn't represent an invariant that we care about maintaining and so I'm just removing it. * Increase FirebaseAuth version for M21.1 This version was missed in the M21.1 version bump PR.

firebase, firebase/firebase-firestore.js.map {\n fail(message);\n }\n}\n\n//# sourceMappingURL=assert.js.map\n\n// CONCATENATED MODULE: . -1;\n if (​cmp < 0) {\n // This node is less than our start key. ignore it\n if (this. Mutations are defined to return the version of the base document\n * only if it is an existing document. NOTE WELL: when you upgrade to this version you NEED to upgrade react and react-test-renderer to version "16.6.1". This patch release fixes a number of crashes, resolves build issues (both for iOS and Android), and brings React to v16.6.1. Thanks everyone who contributed code or participated in the discussion for cherry-picking commits. Changed

Comments
  • Did this become a production issue for you? I found that not enabling offline persistence cleared the error for me, but your point about production sites has me worried.
  • I had the same issue with 5.5.0 and this fixed it.
  • @wtk, This wasn't a prod concern for me since I didn't go into production until AFTER the site was updated.
  • I tried your solution and it solved my problem, but the main draw of this approach is that it increases the number of firestore readings!