i got wired issued with firebase deployment using:
firebase deploy -P dev
the error is
✔ functions[testFunction(us-central1)] Successful update operation.
Invalid source token
looks like its happen to new functions that created
when i tried to deploy specific function using:
firebase -deploy -P dev --only functions:name
its working
when i run and deploy all functions and all my apps i am getting the above error with no information
also the logs from google cloud function is:
status: {
code: 9
message: "Invalid source token"
}
firebase tools version 11.0.0
node: 14.19.3
I would suggest upgrading to atleast node 16 as there's an open issue regarding the "Invalid Source Token" on your current firebase-tools version. There's already a pull request regarding that issue and it will be fixed on the upcoming updates. Here's the github issue for reference.
Related
After removing unused services, I was unable to push the code (amplify push) and got this error.
the command that I run
amplify remove notifications
amplify remove analytics
CLI error (amplify push):
✖ There was an error pulling the backend environment dev.
🛑 not enough bytes in the stream. expected 15644. got only 11274
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: 7afb1bd4-92b7-47dc-a33c-da119f94dfc9
✅ Report saved: /var/folders/6r/4np_tfpj3dbc69f1mc7l2gph0000gn/T/jammaroundapp/report-1674513678504.zip
✔ Done
Project Identifier: 1c09b09cbdd7fadb87731c2182daedce
Error.json
{
"name":"BackendPullFault",
"classification":"FAULT",
"options":{
"message":"not enough bytes in the stream. expected 15644. got only 11274"
},
"downstreamException":{
},
"link":"https://docs.amplify.aws/cli/project/troubleshooting/"
}
I try to pull the AWS Amplify in a new project and got this error "Failed to pull the backend" and also try to update anything on the AWS Amplify dashboard and press on Save and Deploy button but got this error
Deployment failed
not enough bytes in the stream. expected 15644. got only 11274 at AssertByteCountStream._flush
amplify cli version 10.6.2
Upgraded firebase to version 11.15.0 as described here
https://firebase.blog/posts/2022/10/whats-new-at-Firebase-Sumit-2022
==> firebase --version
11.15.0
Ran
==> firebase experiments:enablewebframeworks
Got error
Error: experiments:enablewebframeworks is not a Firebase command
There seems to be a documentation error. There must be a space between the enable & webframeworks
Try to run :
firebase experiments:enable webframeworks
Instead of :
firebase experiments:enablewebframeworks
I tried with firebase experiments:enable webframeworks and was able to execute the command successfully.
You can refer this github link.
I'm following a course of ionic and I need to store a picture on firebase database, at that point we should install firebase-tools, which I do by executing as admin:
npm install -g firebase-tools
But then the course says you should execute:
firebase init
and then I receive the following error:
Error: An unexpected error has occurred.
This generic error with nothing else.
Any ideas of how to solve this?
If you execute:
firebase init --debug
This gives you more info about the error.
It might be something about credentials or login information which can be solved by executing:
firebase login
I'm trying to start new Firebase Functions project using latest versions of packages.
I've followed this tutorial https://youtu.be/DYfP-UIKxH0:
Firebase login
Firebase init
Created functions project the same way as tutorial says
Uncommented index.ts content
After that I get this error:
Starting #google-cloud/functions-emulator
[2018-04-04T19:05:12.124Z] Parsing function triggers
[2018-04-04T19:05:12.404Z] Error while deploying to emulator: TypeError: Cannot read property 'call' of undefined
TypeError: Cannot read property 'call' of undefined
at Promise (/usr/local/lib/node_modules/firebase-tools/node_modules/#google-cloud/functions-emulator/src/client/rest-client.js:34:42)
at getService.then (/usr/local/lib/node_modules/firebase-tools/node_modules/#google-cloud/functions-emulator/src/client/rest-client.js:33:16)
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
⚠ functions: Failed to emulate helloWorld
I have latest functions emulator *1.0.0-beta4.
All other libs are in latest versions...
I'm at point where I have no idea how to debug this better and how to resolve this
This error occurs if an existing process listens on port 5000. Double check if there's a process running, e.g. on Mac OS Sierra
sudo lsof -n -iTCP:5000 | grep LISTEN
Stop this process or run firebase on another port, e.g.
firebase -p 7777 serve --only functions
No need to reinstall packages. Error message is not helpful and we spent some time to find the root cause.
It turned out that it was due other app that was listening on port 5001!
Firebase serve stops with some weird message.
Just check as answer below if ports aren't busy
i am using firebase cli and i try the following
$ firebase init
the cli continue with the message :
You're about to initialize a Firebase project in this directory:
c:\Dev\Test
are you ready to proceed ?
i type y
and choose Hosting:Configure and deploy Firebase Hosting sites
after few second i get the error
Error: Server Error. connect ETIMEDOUT 104.197.85.31:443
what can be the problem ?
my Enviroment specification:
CLI Version: 3.9.1
Platform: win32
Node Version: v7.10.0
Time:Thu Jun 08 2017 18:03:14 GMT+0430 (Iran Daylight Time)
i am useing PSIPHONE also as a proxy but i have also tried without PSIPHONE .
in both cases i get connection timeout
i have pinged 104.197.85.31 the connection is ok .
any suggestion to solve the issue ?
is it because i am in IRAN ?
Just close your terminal and re-run these commands.
firebase login
and now try again
firebase deploy --only hosting
It works for me!!!
I don't know why this is the first result on google but the second result had the answer:
https://stackoverflow.com/a/63832234/3393964
npm i -g firebase-tools
Updating firebase tools worked for me. then, try again firebase deploy.
if it still didn't work try clearing the firebase cache which is the .firebase file
It's on the Firebase's end. You can check status here.
In my case, my work PC started blocking Firebase deploys (Even on my mobile network).
Deploying from my home PC worked just fine.