Firebase-tools: Errors when trying to deploy cloud functions

Created on 12 Oct 2020  路  12Comments  路  Source: firebase/firebase-tools

[REQUIRED] Environment info.

firebase-tools: 8.12.1

Platform: macOS 10.14.6

[REQUIRED] Test case

  1. Run: firebase deploy --only functions:[functionName]

[REQUIRED] Steps to reproduce

  1. Run: firebase deploy --only functions:[functionName]

[REQUIRED] Expected behavior

Deploy the function to the firebase project

[REQUIRED] Actual behavior

Since yesterday I have got different errors:

  • Error: Server Error. connect ETIMEDOUT 172.217.28.106:443

11334d72-1891-4a2c-87e4-20f8a943bf5d

  • Error: Could not read public directory. Remove links and shortcuts and try again.

When put the debug flag I got this information too:

ec11b907-c465-4e63-bafb-359663682e0b

f953ea34-3693-4a77-a7a2-570bc46724ad

I tried to run firebase logout and firebase login again and sometimes the login process gave me errors too:

Screen Shot 2020-10-12 at 10 15 40 AM

Most helpful comment

To add to @aravindvnair99 comment I also have started experiencing this recently with no change to the code.

Functions deploys started to fail intermittently from 03/10/2020.

When deploying I get the same error as above for random functions each deploy. Following the link to the logs the console returns: DENIED: Unable to write blob. This can be resolved by clearing the image for the failed function and redeploying. However it continues to fail on subsequent builds this is happening > 33% of the time.

I am using the Node 12 image it seem to be more reliable with Node 8 however this is now deprecated.

All 12 comments

This issue does not seem to follow the issue template. Make sure you provide all the required information.

@slinkstep see these similar issues:
https://github.com/firebase/firebase-tools/search?q=ETIMEDOUT&type=issues

Unfortunately there is nothing we can do about ETIMEDOUT, it happens when you have a slow or flaky internet connection. I know it's super frustrating but it's not something we can fix within the CLI.

It's happening to all team members and we have stable connections

@slinkstep hmmm now that I am looking at your screenshot I see two different errors:

  1. ETIMEDOUT
  2. input source must be valid Stream or Buffer instance

Which one is the one that's happening to your whole team?

Both of them, as I said, they are random when we try to deploy. Right now we are getting ETIMEDOUT when we use firebase deploy --only functions:XXXX but if we run: gcloud functions deploy XXXXXX it works perfectly

Hmmmm ok the fact that it works with gcloud is fishy. Re-opening.

Any updates ? I haven't been able to deploy any function yet

@samtstern I'm also getting:

```shell
! functions[app(us-central1)]: Deployment error.
Build failed: Build error details not available. Please check the logs at

Functions deploy had errors with the following functions:
app

To try redeploying those functions, run:
firebase deploy --only "functions:app"

To continue deploying other features (such as database), run:
firebase deploy --except functions

Error: Functions did not deploy properly.

To add to @aravindvnair99 comment I also have started experiencing this recently with no change to the code.

Functions deploys started to fail intermittently from 03/10/2020.

When deploying I get the same error as above for random functions each deploy. Following the link to the logs the console returns: DENIED: Unable to write blob. This can be resolved by clearing the image for the failed function and redeploying. However it continues to fail on subsequent builds this is happening > 33% of the time.

I am using the Node 12 image it seem to be more reliable with Node 8 however this is now deprecated.

To add to @aravindvnair99 comment I also have started experiencing this recently with no change to the code.

Functions deploys started to fail intermittently from 03/10/2020.

When deploying I get the same error as above for random functions each deploy. Following the link to the logs the console returns: DENIED: Unable to write blob. This can be resolved by clearing the image for the failed function and redeploying. However it continues to fail on subsequent builds this is happening > 33% of the time.

I am using the Node 12 image it seem to be more reliable with Node 8 however this is now deprecated.

@nikglavin Yes, each time what I am doing now is that I go to the GCP console and then clear the entire bucket. Then it works and fails again sometime down in the future in a few days. It's become a continuous cycle now. I even tried setting life cycle to 1 day and it didn't help. I am using Node 10.

@aravindvnair99 which bucket are you clearing? the archive bucket? I'm having he same issue with a handful of my functions now.

@aravindvnair99 which bucket are you clearing? the archive bucket? I'm having he same issue with a handful of my functions now.

@joerozek I was clearing the artifacts bucket.

Was this page helpful?
0 / 5 - 0 ratings