While running a a deployment for firebase cloud functions, I got this error
Invalid source token.
There seems to be no documentation anywhere about the cause or fixes.
I once experienced this error before.
Re-running the deployments seems to fix the issue.
Related
I'm trying to create fresh Firestore project from my Firestore console, but I get this error, anyone knows how to fix?
Just realized the issue was caused by my CORS(Cross-Origin Resource Sharing), so I turned it off and it got fixed.
While trying to connect Android Studio with a flutter project to Firebase, this error code appeared. After doing A LOT of research, I tried to change my thing, but none seemed to work. I changed my emulator from API 28 to 26 to R, with Nexus 5X which supports Google Play Services. Afterwards, I also added firebase_auth code and cloud_firestore code to pubspec.yaml but it didn't work either. I also tried to change the emulator to Cold Boot but that didn't help. I am really stuck, please HELP!!! Thx :)
Per GitHub post, this error is actually not related to Flutter. In fact, there is an open GitHub issue in Firebase regarding this error. You can check the recommended workarounds here.
I'm trying to get some Firebase functions emulated locally, and have followed Google's local emulator instructions. When I run firebase serve I get this error:
Error from emulator. FirebaseError: HTTP Error: 403,
Mobile SDK API has not been used in project <my project ID>
before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/mobilesdk-pa.googleapis.com/overview?project=<my project ID> then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
Seems straightforward, except that when I follow the supplied URL I get an error because the "Mobile SDK API" does not exist. I've tried searching on Google's API page as well and there is definitely not an API with that name.
Anybody know how I can get around this issue?
(I also tried firebase functions:shell and get the same error)
I got this issue fixed by logging into firebase, since the error was showing on a different machine.
After running firebase login and the authentication process, firebase serve worked without issues.
I was having the same problem and fixed it for myself. I was running Node v11.14.0 and downgraded to the latest version of Node 8 (v 8.16.0).
In my case, the problem was that I was running an outdated version of firebase-tools on the CLI. Running npm update firebase-tools resolved the issue.
No longer able to deploy cloud function via "firebase deploy" command - receiving error: "HTTP Error: 503, The service is currently unavailable"
I previously had a single function deployed and working until a slight modification was causing an authentication error, so I temporarily deleted it until I had time to fix the error.
So a couple days pass, I modify the original code (just added a bit of code relating to service account credentials, didn't even modify the actual function) and tried to re-deploy it (using 'firebase deploy') however it's throwing the following error: "HTTP Error: 503, The service is currently unavailable".
I thought maybe the service is currently down, but Firebase Status Dashboard shows all services are green and noone else seems to be complaining about this error at the moment. I've tried reinstalling/updating firebase-tools and even reverting the functions index.js code back to what it had been when I last successfully deployed, but same error every time. I don't think it has anything to do with the code on my end, but perhaps some weird bug relating to my account/api/authentication.
I've submitted a tech support question on firebase and am awaiting response, but thought I'd try my luck here as well.
Any suggestions?
After some back and forth with firebase technical support, turns out it is some strange bug on their server end (in relation to this particular project) as I'm able to deploy the same functions no problem to other projects. It may have been "triggered" initially by hitting a function invocation quota when I was having issues with one of the functions in the past (an issue which somehow caused the function to be repeatedly called until I realized and deleted it 2 days after). However the project should no longer be limited and I still am unable to deploy any functions on that particular project.
The issue has been handed onto their engineers and hopefully will have it resolved on their end soon.
I am getting a very strange error when I attempt to deploy my firebase functions.
As a test to rule out my code, I deleted everything except the require(firebase-functions); statement in my index.js file and then tried to deploy, but I again received the same error message:
Error: Failed to get status of functions deployments.
It also prompts me to see my function log file, but there is nothing new or relevant outputted there. Anyone have any idea how to fix this?
Please be sure you have the right nodejs version. Also for any issue regarding firebase product, the status can be checked in this link:
https://status.firebase.google.com/
The above link will provide a status for each service.
When the issue gets solved, you can just deploy your functions again with a different name instead of deleting or just redeploy them.
Edit:
Currently in the link above the issue is listed there, there is currently Service Disruption.
Please check this:https://status.firebase.google.com/incident/Functions/18003
to know when this issue will be solved as the firebase team has seen that there is a problem.
firebaser here
There is an ongoing issue with deploying Cloud Functions through the Firebase CLI. To track its status, look a the Firebase status page.
Update: the issue was fixed at 7:22 am PST.
I just successfully deployed some of my own functions, which was failing earlier. Thanks for your reports and patience everyone!
I was getting this error when there were no deployment issues mentioned on the status page.
It turned out that the project just needed to "Link a billing account".
This can be done via the Billing section on Google Cloud Platform.