prameshj

Thanks for reporting this. I tried modifying the demo app in and could not repro this issue. I added `signInAnonymously` in https://github.com/firebase/firebase-js-sdk/blob/547348ba59e1a2bf108330bd882c2ea2753d54d0/packages/auth/demo/src/index.js#L1749 and it returns the same user once signed...

> Seems that at some point Firebase Auth decides to reset the auth data but the client is already signed in!. This is very weird - Does this happen while...

> We don't set any special config settings during Firebase (or Firebase Auth) init - just plain default settings. What is the default persistence method? Does Firebase auth persist data...

> I wasn't sure if its browser policy or the dev tools only showing indexedDB for the main/hosting domain1 and not showing for the Firbebase app's domain2. This is likely...

You're right.. looks like indexedDb doesn't have storage event observer support - https://stackoverflow.com/questions/33237863/get-notified-when-indexeddb-entry-gets-changed-in-other-tab It is possible to poll.. which is what we do in the auth persistence implementation - https://github.com/firebase/firebase-js-sdk/blob/7d23aa4bd1e29d2c10c771c0ab7919b6c5dd2d9b/packages/auth/src/platform_browser/persistence/indexed_db.ts#L354...

Thanks for the additional info! We will try to repro this at our end with additional logs.

We haven't been able to get a repro yet. cc @jbalidiong

Thanks for the update. You're right that logging out does not revoke the idToken automatically. we will document this in the reference docs.

Fair point. The documentation fix was needed at the minimum, but we can make it more easy to find. Revoking the idToken(including all id and refresh tokens for a given...

cc @kevinthecheung @prameshj