I have got this error in Storage "Could not load files; quota has been exceeded for this project"
in the Usage and billing screen its shows no error and all 0%
but its started new day already and I cant access my storage
what is the problem ?
Related
After running for 2 years without hitting any quota limits, My app is hitting a daily quota limit on login (firebase phone authentication) which is not allowing any users to use the app and saying "SMS Quota for this project has been exceeded".
I checked firebase auth usage and its far way from the free tier limit(10K), and also it's on Blaze pay as you go plan.
I also checked Google Cloud Platform quotas page and it shows that all quota are within limit..
GCP support replied the following:
"Cloud Functions quotas are all within limits, the quota exceeded messages are coming from another system."
Any idea haw can this be solved?!
From now on firebase new projects currently have an SMS daily quota of 50 / day.
You can see: firebase console > Authentication > sign-in method
if daily sms are exceeding limit
go to : firebase console > open settings > open usage and billing check your daily limit.
Firebase Identity platform daily limit is 10sms/day
Im using Identity platform in my project
You will find details info about it in the below link
Firebase phone auth daily limit info
"Could not load files; quota has been exceeded for this project? written in my Firebase Storage. I have read some posts about need to delete the files/photos in the storage or upgrade the limit to solve this problem. So, I would like to ask if anyone knows how to delete the photo in storage since, after I exceeded the limit, Firebase Storage does not show any folder or files for me to edit or delete. Even I goto the user's folder manually, still, it does not shows any picture.
It sounds like you've exceeded your bandwidth quota for a day, most likely on a project that is on Firebase's free/Flame plan.
If you wait until tomorrow, the quota will reset and you should be able to read and delete files again (until you go over the daily quota again of course).
Alternatively, you can upgrade to the paid plan, and you'll immediately be able to read and write the files again.
I´m trying to uninstall a resize image firebase extension, but it's showing some error message:
ext-storage-resize-images#zzz.iam.gserviceaccount.com","status":"INVALID_ARGUMENT","statusMessage":"Bad Request","requestPath":"https://cloudfunctions.googleapis.com/v1/projects/zzz/locations/us-central1/functions","httpMethod":"POST"}}
Firebase console logs
{"#type":"type.googleapis.com/google.cloud.audit.AuditLog","status":{"code":3,"message":"Invalid function service account requested: ext-storage-resize-images#zzz.iam.gserviceaccount.com"},"authenticationInfo":{"principalEmail":"1072297581434#cloudservices.gserviceaccount.com","serviceAccountDelegationInfo":[{"firstPartyPrincipal":{"principalEmail":"cloud-dm#prod.google.com"}}]},"requestMetadata":{"callerIp":"64.233.172.179","callerSuppliedUserAgent":"Google-Deployment-Manager,gzip(gfe),gzip(gfe)","requestAttributes":{"time":"2020-07-22T15:01:22.851Z","auth":{}},"destinationAttributes":{}},"serviceName":"cloudfunctions.googleapis.com","methodName":"google.cloud.functions.v1.CloudFunctionsService.CreateFunction","authorizationInfo":[{"resource":"projects/zzz/locations/us-central1/functions/ext-storage-resize-images-generateResizedImage","permission":"cloudfunctions.functions.create","granted":true,"resourceAttributes":{}}],"resourceName":"projects/zzz/locations/us-central1/functions/ext-storage-resize-images-generateResizedImage","request":{"#type":"type.googleapis.com/google.cloud.functions.v1.CreateFunctionRequest","location":"projects/zzz/locations/us-central1","function":{"serviceAccountEmail":"ext-storage-resize-images#zzz.iam.gserviceaccount.com","eventTrigger":{"resource":"projects/_/buckets/zzz.appspot.com","eventType":"google.storage.object.finalize"},"runtime":"nodejs8","description":"Listens for new images uploaded to your specified Cloud Storage bucket, resizes the images, then stores the resized images in the same bucket. Optionally keeps or deletes the original images.","entryPoint":"generateResizedImage","sourceArchiveUrl":"gs://firebase-mod-sources-prod/a139bcfefbf19e901b67789105a3841ed208c6e449a896bafcc4a01e43c07844","availableMemoryMb":1024,"name":"projects/zzz/locations/us-central1/functions/ext-storage-resize-images-generateResizedImage","labels":{"deployment-tool":"firebase-extensions","goog-firebase-ext":"storage-resize-images","goog-firebase-ext-iid":"storage-resize-images"}}},"resourceLocation":{"currentLocations":["us-central1"]}}
The Crashlytics dashboard is showing Crash-free statistics but there is no crash in the ISSUES table.
Knowns:
Latest Fabric and Crashlytics following the Firebase tutorial
Forced a crash using Crashlytics.sharedInstance().crash()
In appdelegate I set FirebaseApp.configure()
App is not on Appstore, but I uploaded the dsyms from the xarchive package
That can happen from time and here's why - when a session ends in a crash, the small amount of data that needs to be sent to know that the crash occurred can safely be sent. However, the crash report is larger, so it can't be sent safely until your users relaunch the app. Once your users do that, the crash report will be sent and you'll be able to dive into the details. Let me know if that clears it up or if you have any other questions!
I started to get following quota exceeded error
Error: HTTP Error: 429, Quota exceeded for quota group 'ReadGroup' and limit 'CLIENT_PROJECT-100s' of service 'cloudresourcemanager.googleapis.com' for consumer 'project_number:563584335***'.
when I tried to deploy functions using firebase-cli
firebase deploy --only functions --token $FIREBASE_TOKEN
I changed the value of FIREBASE_TOKEN thinking that it might have expired. deploy worked for one time after changing token but then again cli tools again started giving above error. Also, I checked quotas but couldn't find any value that exceed the quota limit. My project is on blaze plan (pay as you go).
Maybe I'm missing something? Could anyone help me out on when exactly this error comes and how to fix it?
This is a known problem being addressed by the Firebase team.
In the future, when you have a problem deploying with the Firebase CLI, you should file a bug report with Firebase support so they can collect information.