Handle failure to verify refreshed token #679
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the existing token is expired, and we refresh it successfully, we still need to call
veirfyIdToken
in order to get thefirebaseUser
, which is required bycreateUser
below.Currently, if
verifyIdToken
with the newly refreshed token fails, the error handler is called, but the code passes through, callingcreateUser
with atoken
butfirebaseUserAdminSDK: undefined
, which causes the following error:In order to prevent this, we need to set
newTokenFailure = true
in caseverifyIdToken
fails with the newly refreshed token.FWIW this never happened to me in production, but happens quite often when developing with the Firebase emulators.