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.
When i run firebase init, I selected items blow.

1. Are you ready to proceed?

   Y

2. Which Firebase features do you want to set up for this directory? Press sapce to select features, then Enter to confirm your choice.

   Firestore : Configure security rules and indexed files for Firestore
   Hosting : Configure files for Firebase Hosting and (Optionally) set up GitHub Action deploy (I made firestore)
   Storage : Configure a security rules file for Cloud Storage (I made storage)

3. Please select an option

   Use an existing project ( After that i choice my project which i made)

4. What file should be used for Firestore Rules?

   firestore.rules

5. What file shoul be used for Firestore indexes?

   firestore.indexes.json

6. What do you want to use as your public directory?

   public

7. Configure as a single-page app (rewrite all urls to /index.html)?

   Y

8. Set up automatic builds and deploys with GitHub?

   N

9. File public/index.html already exists. Overwrite?

   N

10. What file should be used for Storage Rules?

    storage.rules

After finish initialization, i run firebase deploy but i met error like this

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 '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

I also encountered this issue when I tried to deploy my website to Firebase's hosting with Firestore and Storage.

When I followed the link and tried to create an app instance? But it appears to be an error as follows:

However, I've deployed using --except storage. It can be deployed without this 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!

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

Same here. The issue still persists with service account GOOGLE_APPLICATION_CREDENTIALS for my case.

Have the same error, when doing firebase deploy and my project has database, hosting and storage.
However firebase deploy --only database,hosting works ok, while firebase deploy --only storage gives that 403 error.
Hope it helps!

Have the same error. firebase deploy returns a read access error:
Error: HTTP Error: 403, Read access to project 'thedjs-a9416' was denied: please check billing account associated and retry
I read the above user's comment and used his workaround.

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 firebase deploy --debug? Passing the --debug flag provides a more detailed log. Also, please remove any PII (personal identifiable information) if needed.

Thanks @aalej! Upgrading to v12.4.0 did the trick!
The only thing, when using yarn, use this command to upgrade firebase-tools, and not npm:
yarn global add firebase-tools

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:

 firebase deploy --only function

!  functions: Upload Error: HTTP Error: 403, Write access to project was denied: please check billing account associated and retry

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

1. Add billing account on https://console.cloud.google.com/billing
2. Change billing plan of your firebase project in Usage and billing > Details & settings > Modify plan > Choose Pay as you go plan