-
Notifications
You must be signed in to change notification settings - Fork 956
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
HTTP Error: 403, Read access to project <project-name> was denied: please check billing account associated and retry #5955
Comments
me paso lo mismo...que onda?? |
Hi @daniel18acevedo, thanks for reporting this issue. I was able to reproduce the behavior mentioned. That said, I’ll notify our team about this so that they can take a look. I’ll also mark this issue as reproducible. |
I have a same issue. I tried log out after log in but it doesn't work too. and I tried firebase init again. if you solve this problem could you tell about it? |
@basinibi I tried the same things you did with no luck, also couldn't fix it so the only thing we can do is to wait. The worst thing is that three days ago was working that command 😔 |
For now, while we're investigating this, if anyone else is encountering a similar issue, please comment +1 or react on the original post so that we can keep track on how many are affected. Apologies for the issues this has caused. |
me paso lo mismo y aun no he podido encontrar una solucion, si alguien sabe algo estare atento, gracias |
I share my case in here to wish this can little help for them.
After finish initialization, i run There was an issue deploying your functions. Verify that your project has a Google App Engine instance setup at https://console.cloud.google.com/appengine and try again. If this issue persists Error: HTTP Error: 403, Read access to project 'my project name' was denied: please check billing account associated and retry |
I have the exact same issue. |
I encountered the same issue |
Mismo error |
Same issue here |
The error was solved when using: firebase deploy --only storage, but is not solve when using a service account credential, more specific, when using the github action: w9jds/firebase-action@master with GCP_SA_KEY |
i used the command firebase deploy --only hosting and work for me! |
Same here. The issue still persists with service account |
Have the same error, when doing |
Have the same error. |
Hey everyone! For those who are experiencing the issue, could you try updating to the latest version of firebase-tools, which is currently v12.4.0. There was a change in that release which switched the checking of default bucket from the App Engine API to the Firebase API. I'm unable to reproduce the issue using v12.4.0 of firebase-tools. For anyone still encountering the error after updating to the latest version, could you share with us the output of running |
Thanks @aalej! Upgrading to v12.4.0 did the trick! |
I had the same error but updating firebase with -- npm install -g firebase-tools -- solved the problem for me and -- firebase deploy -- worked like a charm as usual afterwards. |
Hey, does anybody still face this issue? Upgraded to latest firebase-tools but it gives the same error:
|
It doesn't work for me after updating the firebase tools etc. As I checked the Google cloud console again, it showed a payment issue. After updating the card, it started working. |
Following these steps solves my problem
|
Environment info
Firebase-tools version: 11.27.0 and 12.3.1
OS: Windows
Platform:
Test case
I create a simple firebase project, enable storage service
Steps to reproduce
Login to firebase with firebase-tools then I do the following:
Also the same error happens when try to deploy using the github action (w9jds/firebase-action@master) with an account service key
Expected behavior
Storage rules gets deployed
Actual behavior
There was an issue deploying your functions. Verify that your project has a Google App Engine instance setup at https://console.cloud.google.com/appengine and try again. If this issue persists, please contact support.
Error: HTTP Error: 403, Read access to project '' was denied: please check billing account associated and retry
The text was updated successfully, but these errors were encountered: