firebase init firestore not work with existing project

[JuanOrtizOvied]

DESCRIPTION

work very well with version 10.0.1

firebase login --no-localhost

**version 10.0.1 **

open https://accounts.google.com/o/oauth2....

** version 10.2.2 **

open https://auth.firebase.tools/login?code=....

[REQUIRED] Environment info

firebase-tools: 10.2.2

Platform: ubuntu 20

[REQUIRED] Test case

[REQUIRED] Steps to reproduce

firebase login --no-localhost

firebase init firestore

[REQUIRED] Expected behavior

create firebase.rules file

[REQUIRED] Actual behavior

Error: It looks like you haven't used Cloud Firestore in this project before. Go to https://console.firebase.google.com/project/<PROJECT-ID>/firestore to create your Cloud Firestore database.

[yuchenshi]

Have you enabled Cloud Firestore on your existing project before you tried this? If so, this is definitely a bug or a permission issue (and please let us know if you're using a non-Admin account or service account). If not, please follow the link which explains about setting up Firestore.

[JuanOrtizOvied]

Yes, I created my firestore database one month ago.

[bkendall]

To confirm the type of issue, can you run the command with --debug and provide the last bit of output? It's likely there's an HTTP request that's returning some type of error or a check that's being made that's incorrect. Thanks!

[JuanOrtizOvied]

@bkendall

[2022-03-08T19:10:53.980Z] > refreshing access token with scopes: ["email","https://www.googleapis.com/auth/cloud-platform","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","openid"]
[2022-03-08T19:10:53.980Z] >>> HTTP REQUEST POST https://www.googleapis.com/oauth2/v3/token  
 <request body omitted>
[2022-03-08T19:10:54.537Z] <<< HTTP RESPONSE 400 {"cache-control":"no-cache, no-store, max-age=0, must-revalidate","date":"Tue, 08 Mar 2022 19:10:54 GMT","expires":"Mon, 01 Jan 1990 00:00:00 GMT","pragma":"no-cache","content-type":"application/json; charset=utf-8","vary":"X-Origin, Referer, Origin,Accept-Encoding","server":"scaffolding on HTTPServer2","x-xss-protection":"0","x-frame-options":"SAMEORIGIN","x-content-type-options":"nosniff","alt-svc":"h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\"","accept-ranges":"none","transfer-encoding":"chunked"}
[2022-03-08T19:10:54.539Z] >>> HTTP REQUEST GET https://appengine.googleapis.com/v1/apps/eventos-staging-93d3a  
 
[2022-03-08T19:10:55.280Z] <<< HTTP RESPONSE 401 {"www-authenticate":"Bearer realm=\"https://accounts.google.com/\", error=\"invalid_token\"","vary":"X-Origin, Referer, Origin,Accept-Encoding","content-type":"application/json; charset=UTF-8","date":"Tue, 08 Mar 2022 19:10:55 GMT","server":"ESF","cache-control":"private","x-xss-protection":"0","x-frame-options":"SAMEORIGIN","x-content-type-options":"nosniff","alt-svc":"h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\"","accept-ranges":"none","transfer-encoding":"chunked"}
[2022-03-08T19:10:55.281Z] <<< HTTP RESPONSE BODY {"error":{"code":401,"message":"Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","status":"UNAUTHENTICATED"}}
[2022-03-08T19:10:55.282Z] error getting database typeHTTP Error: 401, Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. {"name":"FirebaseError","children":[],"context":{"body":{"error":{"code":401,"message":"Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","status":"UNAUTHENTICATED"}},"response":{"statusCode":401,"body":{"error":{"code":401,"message":"Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","status":"UNAUTHENTICATED"}},"headers":{"www-authenticate":"Bearer realm=\"https://accounts.google.com/\", error=\"invalid_token\"","vary":"X-Origin, Referer, Origin,Accept-Encoding","content-type":"application/json; charset=UTF-8","date":"Tue, 08 Mar 2022 19:10:55 GMT","server":"ESF","cache-control":"private","x-xss-protection":"0","x-frame-options":"SAMEORIGIN","x-content-type-options":"nosniff","alt-svc":"h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\"","accept-ranges":"none","transfer-encoding":"chunked"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"appengine.googleapis.com","port":443,"hostname":"appengine.googleapis.com","hash":null,"search":null,"query":null,"pathname":"/v1/apps/eventos-staging-93d3a","path":"/v1/apps/eventos-staging-93d3a","href":"https://appengine.googleapis.com/v1/apps/eventos-staging-93d3a"},"method":"GET"}}},"exit":1,"message":"HTTP Error: 401, Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","status":401}
[2022-03-08T19:10:55.290Z] database_type: undefined

Error: It looks like you haven't used Cloud Firestore in this project before. Go to https://console.firebase.google.com/project/eventos-staging-93d3a/firestore to create your Cloud Firestore database.

[terasaka2k]

This seem to be a degration occurred from v10.2.0, from which some OAuth scopes are missing compared to login without --no-localhost option.

[sebastien-f]

I just had the same error, with the exact same context. I have the issue with 10.4.2.
Reverted to 10.1.5, it didn't work, so I logged out, logged in again and there it worked.