Firebase-tools: Please run firebase login --reauth (when using FIREBASE_TOKEN)

[heygambo]

I've removed and reinstalled firebase-tools using npm and yarn.
For some reason even after running firebase login --reauth it will still complain about it.

⚠ Your CLI authentication needs to be updated to take advantage of new features.
⚠ Please run firebase login --reauth

versions:
firebase-tools 3.9.0
node v7.2.1
nvm 0.33.0

Does anyone know how to get rid of this warning?

[justinbmeyer]

yes, I'm seeing the same problem. Any resolution? (edit, this was because I used the project name, not the id).

[heygambo]

I'm still getting:

✔  Database Rules for abc have been downloaded to database.rules.json.
Future modifications to database.rules.json will update Database Rules when you run
firebase deploy.

=== Functions Setup

A functions directory will be created in your project with a Node.js
package pre-configured. Functions can be deployed with firebase deploy.


Error: This command requires new authorization scopes not granted to your current session. Please run firebase login --reauth

Running reauth doesn't help.

[heygambo]

After months I have finally found the issue.

I've had export FIREBASE_TOKEN=abc in my ~/.zshenv file and forgot about it.

Now everything works fine!

I wish there would have been a note that I'm using my FIREBASE_TOKEN or that this is something I should have looked for.

e.g.

⚠ Your CLI authentication needs to be updated to take advantage of new features.
⚠ Note that you're using the FIREBASE_TOKEN environment variable.
⚠ Please renew or remove that and try again.

[muhammadghazali]

Another way that works for me to work around this issue is by logging out and re-login the Firebase CLI.

[heygambo]

Another way that works for me to work around this issue is by logging out and re-login the Firebase CLI.

This was my first guess as well. But if that doesn't work, then have a look at the terminal environment variables.

[mohanramphp]

I found what was the problem. Please follow steps below

Step 1 Create firebase project @ Firebase console
Step 2 Login into firebase via cmd firebase login
Step 3 Run firebase init Initialize app by selecting existing app you created in Step 1
Step 4 Run firebase deploy should deploy your application

[heygambo]

I found what was the problem. Please follow steps below
Step 1 Create firebase project @ Firebase console
Step 2 Login into firebase via cmd firebase login
Step 3 Run firebase init Initialize app by selecting existing app you created in Step 1
Step 4 Run firebase deploy should deploy your application

This was my first guess as well. But if that doesn't work, then have a look at the terminal environment variables.

This ticket is still open because of my suggestion to add a note about old firebase tokens:
https://github.com/firebase/firebase-tools/issues/342#issuecomment-314994814

[mohanramphp]

@nerdyglasses I face same issue and once i created project first in firebase console and then it worked. Can you brief what sequence or steps to reproduce your issue

[heygambo]

@mohanramphp put this in your .bashrc or .zshrc, then start a new terminal session:
export FIREBASE_TOKEN=94th393g8h2g23g

and run firebase deploy.

[alltej]

What works for me is to run firebase logout and then login with firebase login.

[heygambo]

@alltej did you have a FIREBASE_TOKEN from firebase 2 in your shell's environment?
My point is that this will make the firebase 3 cli break.

[Overdrivr]

I got this error by passing a wrong project id to the -P flag.

Basically, I thought I could define projects in my firebaserc file like this:

{
  "projects": {
    "staging": "firebase-staging-project-id"
    "production": "firebase-production-project-id"
  }
}

And call

firebase deploy --token "$FIREBASE_TOKEN" -P staging

But it fails with the error described here.

While passing the full project id like below

firebase deploy --token "$FIREBASE_TOKEN" -P firebase-staging-project-id

works without problem. So maybe this P flag should need a more informative message ? Also, is this the expected behavior or a bug ?

[NikolaJankovic]

I had the same issue as @Overdrivr - passing the wrong project name raised the auth prompt and 500 error subsequently.

Passing an invalid project name should really be caught and have a more appropriate error message.

[mmorrison24]

I am getting this error without attempting to use a FIREBASE_TOKEN param.

have tried to
`relogin,

--reauth,

creating and deploying another test project

upgrading all packages

and to delete and reinit firebase`

my firebase-debug.log looks like this

my npm debug.log looks like this

Any ideas?

[heygambo]

@mmorrison24 make sure it's not in your export list in the terminal.

run export and see if there is a FIREBASE_TOKEN outputted.

[philip-firstorder]

I ran export but there is no FIREBASE_TOKEN, still getting the error

[guruprasaad123]

In my case am unable to evenlogin.
So CLI wont allow me to even initialize a project.
Looks like am trapped.

[bkendall]

I see that the original error (regarding FIREBASE_TOKEN) was resolved. There's still some questions regarding warning when using the environment to authenticate, which is actually something that is currently being worked on internally (though, slowly). I'm closing this issue as there's not been recent activity on it. If anyone is still having issues with authentication, I'd ask that you open a new bug with the appropriate information! Thanks!

[BuddhaNag12]

In my case am unable to evenlogin.
So CLI wont allow me to even initialize a project.
Looks like am trapped.

i'm having the same problem please suggest a help

[bkendall]

@BuddhaNag12 please open a new issue so we can better track this. Thank you.

[kichus14]

Use firebase login --no-localhost. This will prompt to paste the authorization code displayed in the screen after successful login

[Josephpious]

Copy the code and paste but it still give error