Skip to content
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

Firestore appears offline after fetching auth token failed: getToken aborted due to token change error

Closed
aggarwalvinayak opened this issue Jun 6, 2020 · 14 comments · Fixed by #3193

Comments

@aggarwalvinayak
Copy link

aggarwalvinayak commented Jun 6, 2020

[2020-06-06T14:37:20.739Z] @firebase/firestore: Firestore (7.15.0): Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: FirebaseError: [code=unknown]: Fetching auth token failed: getToken aborted due to token change.
This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.

Found this bug while using .get() in a document. Not able to even get the full database with collection. Was working few hours ago.. Found that other users also experienced this while using this version. Was fixed after moving to a previous version of it.

[REQUIRED] Describe your environment

  • Operating System version: Ubuntu 20.04
  • Browser version: Chrome 81.0.4044.122 (Official Build) (64-bit)
  • Firebase SDK version: 7.15
  • Firebase Product: firestore (auth, database, storage, etc)

[REQUIRED] Describe the problem

Steps to reproduce:

To reproduce try to get any data from the firestore using .collection().doc().get()

Relevant Code:

https://stackblitz.com/fork/firebase-issue-sandbox

getCookieFromDatabase=(uid)=>{
      this.database.collection("users").doc(uid).get()
      .then((curdoc)=>{
        console.log(curdoc.data().cookie)
        return curdoc.data().cookie;
      })
    }```
@google-oss-bot
Copy link
Contributor

google-oss-bot commented Jun 6, 2020

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

@jadengis
Copy link

jadengis commented Jun 7, 2020

I am receiving this error as well, but only on the first read attempted as my application boots. Subsequent reads go through well, but this error is completely breaking my linking into my app (data isn't resolved on application load).

@MieleVL
Copy link

MieleVL commented Jun 7, 2020

Same here. I even get occasional document read errors saying that 'the client is offline', while it surely isn't. I believe this is happening when a read is executed shortly after or during a token refresh. This makes our application completely unreliable and not suitable for production environments.

@raoufswe
Copy link

raoufswe commented Jun 7, 2020

I'm facing the same issue too.

@wilhuff wilhuff changed the title [2020-06-06T14:37:20.739Z] @firebase/firestore: Firestore (7.15.0): Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: FirebaseError: [code=unknown]: Fetching auth token failed: getToken aborted due to token change. This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend. Firestore appears offline after fetching auth token failed: getToken aborted due to token change error Jun 7, 2020
@wilhuff
Copy link
Contributor

wilhuff commented Jun 7, 2020

Hi @aggarwalvinayak, I'm sorry to hear you're having difficulty.

Your link to stackblitz is just a general starter project and contains no code.

This kind of error can only happen in combination with Firebase Auth. Could you show how your Firestore code is interacting with Firebase Auth? Also could you enable logging and show what you see?

In general you need to wait for auth to complete before calling Firestore to avoid problems of this nature, though it seems like you'd have to be doing that to pass the uid to getCookieFromDatabase.

@wilhuff
Copy link
Contributor

wilhuff commented Jun 7, 2020

Using the following code in a simple html page, I can't reproduce the issue:

const firebaseConfig = {
  // ...
};

async function main() {
  firebase.initializeApp(firebaseConfig);

  await firebase.auth().signInAnonymously();

  const db = firebase.firestore();
  firebase.firestore.setLogLevel('debug')

  const snap = await db.collection('foo').doc('bar').get();
  console.log(`Found document: exists=${snap.exists}, data=${JSON.stringify(snap.data())}`);
}

main()
  .then(() => {
    console.log('Success!');
  })
  .catch((e) => {
    console.log(`Failure: ${e}`);
  });

@aggarwalvinayak
Copy link
Author

aggarwalvinayak commented Jun 8, 2020

Sorry i dont know how the stackblitz link got posted. Might be in the demo issue template.
The error was in the getCookieFromDataBase function in https://github.com/aggarwalvinayak/News-WebApp/blob/Guest%2BGoogle_User/news-app/src/components/Firebase/Firebase.ts
I cannot use the Html since I was working with React. I think it is a bug in the current version of Firestore, as other people also mentioned above I was also getting the error on the first Read from the database immediately after Authentication. My app crashed so could not proceed for further reads.
The issue can be reproduced if the dependency of the above project (https://github.com/aggarwalvinayak/News-WebApp/blob/Guest%2BGoogle_User/ ) is changed to firebase@7.15.0 instead of the current downgraded version, after signing in the redirection leads to a page which tries to reads and there is a error at that time in the console.

@gitCoy
Copy link

gitCoy commented Jun 8, 2020

I got it, too!
firebase version 7.15.0
I'm change to v7.14.2, the issue is resolve

@schlakob
Copy link

schlakob commented Jun 8, 2020

I got the same issue and I code with Vue.js.

I tried the simple example of @wilhuff like that:

async initApp () {
        console.log("-----------------------------Start init-----------------------------")
        const firebaseConfig = {
              //my configs
        }

        firebase.initializeApp(firebaseConfig)
        firebase.firestore.setLogLevel('debug')
        console.log("-----------------------------Finished init-----------------------------")
},
async testFunction() {
        console.log("-----------------------------Try login and test collection ---------------------------------")
        await firebase.auth().signInWithEmailAndPassword("********", "********")

        const db = firebase.firestore()

        const snap = await db.collection('rezepte').doc('test').get()
        console.log(`Found document: exists=${snap.exists}, data=${JSON.stringify(snap.data())}`)
        console.log("-----------------------------Finished login and test collection ----------------------------------------")
}

But here is my console log:

-----------------------------Start init-----------------------------
Home.vue?76f2:59 -----------------------------Finished init-----------------------------
Home.vue?76f2:62 -----------------------------Try login and test collection ---------------------------------
localhost/:1 A cookie associated with a cross-site resource at http://google.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
localhost/:1 A cookie associated with a cross-site resource at https://google.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
index.esm.js?abfd:106 [2020-06-08T21:54:29.096Z]  @firebase/firestore: Firestore (7.15.0): FirestoreClient Initializing. user= Rdzxh2sZTPPANhrJJ80GJPusPRH2
index.esm.js?abfd:106 [2020-06-08T21:54:29.099Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Get next mutation batch
index.esm.js?abfd:106 [2020-06-08T21:54:29.102Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Allocate target
index.esm.js?abfd:106 [2020-06-08T21:54:29.103Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Execute query
index.esm.js?abfd:106 [2020-06-08T21:54:29.103Z]  @firebase/firestore: Firestore (7.15.0): IndexFreeQueryEngine Using full collection scan to execute query: Query(target=Target(rezepte/test, orderBy: [__name__ (asc)]); limitType=F)
index.esm.js?abfd:106 [2020-06-08T21:54:29.106Z]  @firebase/firestore: Firestore (7.15.0): Connection Creating WebChannel: https://firestore.googleapis.com/google.firestore.v1.Firestore/Listen/channel [object Object]
index.esm.js?abfd:106 [2020-06-08T21:54:29.110Z]  @firebase/firestore: Firestore (7.15.0): Connection Opening WebChannel transport.
index.esm.js?abfd:106 [2020-06-08T21:54:29.112Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel sending: {"database":"projects/rezeptbuch-18dac/databases/(default)","addTarget":{"documents":{"documents":["projects/rezeptbuch-18dac/databases/(default)/documents/rezepte/test"]},"targetId":2}}
index.esm.js?abfd:106 [2020-06-08T21:54:29.145Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel transport opened.
index.esm.js?abfd:106 [2020-06-08T21:54:29.174Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel received: {"targetChange":{"targetChangeType":"ADD","targetIds":[2]}}
index.esm.js?abfd:106 [2020-06-08T21:54:29.227Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel received: {"documentChange":{"document":{"name":"projects/rezeptbuch-18dac/databases/(default)/documents/rezepte/test","fields":{"test":{"stringValue":"test"}},"createTime":"2020-06-08T21:41:38.124514Z","updateTime":"2020-06-08T21:41:38.124514Z"},"targetIds":[2]}}
index.esm.js?abfd:106 [2020-06-08T21:54:29.227Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel received: {"targetChange":{"targetChangeType":"CURRENT","targetIds":[2],"resumeToken":"CgkIp/GTvZrz6QI=","readTime":"2020-06-08T21:54:27.994791Z"}}
index.esm.js?abfd:106 [2020-06-08T21:54:29.228Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel received: {"targetChange":{"resumeToken":"CgkIp/GTvZrz6QI=","readTime":"2020-06-08T21:54:27.994791Z"}}
index.esm.js?abfd:106 [2020-06-08T21:54:29.229Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Get last remote snapshot version
index.esm.js?abfd:106 [2020-06-08T21:54:29.231Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Apply remote event
index.esm.js?abfd:106 [2020-06-08T21:54:29.233Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: notifyLocalViewChanges
index.esm.js?abfd:106 [2020-06-08T21:54:29.237Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Release target
Home.vue?76f2:68 Found document: exists=true, data={"test":"test"}
Home.vue?76f2:69 -----------------------------Finished login and test collection ----------------------------------------
index.esm.js?abfd:106 [2020-06-08T21:54:29.238Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel sending: {"database":"projects/rezeptbuch-18dac/databases/(default)","removeTarget":2}
index.esm.js?abfd:106 [2020-06-08T21:54:29.284Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel received: {"targetChange":{"targetChangeType":"REMOVE","targetIds":[2]}}
Home.vue?76f2:62 -----------------------------Try login and test collection ---------------------------------
index.esm.js?abfd:106 [2020-06-08T21:54:44.669Z]  @firebase/firestore: Firestore (7.15.0): FirestoreClient Credential Changed. Current user: Rdzxh2sZTPPANhrJJ80GJPusPRH2
index.esm.js?abfd:106 [2020-06-08T21:54:44.669Z]  @firebase/firestore: Firestore (7.15.0): RemoteStore RemoteStore restarting streams for new credential
index.esm.js?abfd:106 [2020-06-08T21:54:44.672Z]  @firebase/firestore: Firestore (7.15.0): Connection WebChannel transport closed
index.esm.js?abfd:106 [2020-06-08T21:54:44.673Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Get next mutation batch
index.esm.js?abfd:106 [2020-06-08T21:54:44.674Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Allocate target
index.esm.js?abfd:106 [2020-06-08T21:54:44.674Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Execute query
index.esm.js?abfd:106 [2020-06-08T21:54:44.674Z]  @firebase/firestore: Firestore (7.15.0): IndexFreeQueryEngine Using full collection scan to execute query: Query(target=Target(rezepte/test, orderBy: [__name__ (asc)]); limitType=F)
index.esm.js?abfd:106 [2020-06-08T21:54:44.676Z]  @firebase/firestore: Firestore (7.15.0): PersistentStream stream callback skipped by getCloseGuardedDispatcher.
index.esm.js?abfd:106 [2020-06-08T21:54:44.676Z]  @firebase/firestore: Firestore (7.15.0): PersistentStream close with error: FirebaseError: [code=unknown]: Fetching auth token failed: getToken aborted due to token change.
index.esm.js?abfd:106 [2020-06-08T21:54:44.676Z]  @firebase/firestore: Firestore (7.15.0): OnlineStateTracker Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: FirebaseError: [code=unknown]: Fetching auth token failed: getToken aborted due to token change.
This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
index.esm.js?abfd:106 [2020-06-08T21:54:44.677Z]  @firebase/firestore: Firestore (7.15.0): FirestoreClient Credential Changed. Current user: Rdzxh2sZTPPANhrJJ80GJPusPRH2
index.esm.js?abfd:106 [2020-06-08T21:54:44.677Z]  @firebase/firestore: Firestore (7.15.0): RemoteStore RemoteStore restarting streams for new credential
index.esm.js?abfd:106 [2020-06-08T21:54:44.679Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Get next mutation batch
index.esm.js?abfd:106 [2020-06-08T21:54:44.679Z]  @firebase/firestore: Firestore (7.15.0): Connection Creating WebChannel: https://firestore.googleapis.com/google.firestore.v1.Firestore/Listen/channel [object Object]
index.esm.js?abfd:106 [2020-06-08T21:54:44.680Z]  @firebase/firestore: Firestore (7.15.0): MemoryPersistence Starting transaction: Release target

I wrote two different functions, because of the problem, that only from the second (third, ..., nth) request on it's not working anymore. If you log in the first time everything works fine. When I clear the Browsers Storage (IndexdDB) I can start with one working attempt again.
BTW: I dont get any issues if I use the signInAnonymously() function. Maybe because it is always like a "first login".

So you can see the first attempt works fine (how it should) and the second gets this error:

index.esm.js?abfd:106 [2020-06-08T21:54:44.676Z]  @firebase/firestore: Firestore (7.15.0): OnlineStateTracker Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: FirebaseError: [code=unknown]: Fetching auth token failed: getToken aborted due to token change.
This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.

@estebanrao
Copy link

estebanrao commented Jun 8, 2020

Having the same issue with v7.15.0 on a React app with redux-saga


export function* signInWithGoogle() {
  try {
    const { user } = yield auth.signInWithPopup(googleProvider);
    const userRef = yield call(createUserProfileDocument, user);
    const userSnapshot = yield userRef.get();

    yield put(
      googleSignInSuccess({ id: userSnapshot.id, ...userSnapshot.data })
    );
  } catch (error) {
    yield put(googleSignInFailure(error));
  }
}

Downgrading to v7.14.2 as @gitCoy mentioned fixed the issue

@wilhuff
Copy link
Contributor

wilhuff commented Jun 8, 2020

@schlakob Thanks for your notes. I'm able to reproduce the error you've seen.

It turns out that this error first occurs in 7.14.6. #3184 treats the symptom, but there's been a change in behavior here that I'll be able to track down based on this.

Here's my reproduction:

const firebaseConfig = {
  // ...
};
firebase.initializeApp(firebaseConfig);

async function testFunction() {
  await firebase.auth().signInWithEmailAndPassword('****', '****');

  const db = firebase.firestore();
  firebase.firestore.setLogLevel('debug')

  const doc = db.collection('foo').doc('bar');
  const snap = await doc.get();
  console.log(`Found document: exists=${snap.exists}, data=${JSON.stringify(snap.data())}`);
}

async function main() {
  await testFunction();
  await testFunction();
}

main()
  .then(() => {
    console.log('Success!');
  })
  .catch((e) => {
    console.log(`Failure: ${e}`);
  });

@schmidt-sebastian
Copy link
Contributor

schmidt-sebastian commented Jun 9, 2020

We were able to verify that this has been fixed with #3184, which should be released this week.

@meerkat-citronella
Copy link

meerkat-citronella commented Jun 12, 2020

I am receiving this error as well, but only on the first read attempted as my application boots. Subsequent reads go through well, but this error is completely breaking my linking into my app (data isn't resolved on application load).

*bump. This issue fixes for me after signing a user out. But that is not a workable solution.

@Ridermansb
Copy link

Ridermansb commented Jun 13, 2020

@firebase firebase locked and limited conversation to collaborators Jul 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet