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

We have had same problem and few more with 9.4.0 and reverted to 9.3.0 to get our deploys working again.

• error in deploy, success in cloud console
• error in deploy, in progress in cloud console (subsequent retry failed because HTTP Error: 400, An operation on function ... is already in progress
• reporting error for one function from a batch and not reporting status of the rest of the batch
• 9.4.0 is creating new functions without Allow unauthenticated flag, 9.3.0 is using it. I believe this is not documented anywhere

Hi @ljle, thanks for reporting this. It looks like the issue here is that the function you deployed is taking longer to deploy than our timeout on polling the operation. I'll make a PR to increase this timeout, which should help.

@m4recek I think the first 2 issues are related to this timeout - I'll take a closer look into the other 2 shortly.

@m4recek

• reporting error for one function from a batch and not reporting status of the rest of the batch

Could you open a separate issue for this and include logs of what you're seeing? I think I identified one issue with the code that might cause this, but I want to make sure its actually what you are seeing,

• 9.4.0 is creating new functions without Allow unauthenticated flag, 9.3.0 is using it. I believe this is not documented anywhere

On further inspection, I think this is related to the same timeout issue - we set the necessary IAM policy to 'allow unauthenticated' for new functions here: https://github.com/firebase/firebase-tools/blob/master/src/deploy/functions/tasks.ts#L81, but it the operation polling times out, this will never be run.

Experienced same problems on 9.4.0. Trying multiple functions deploy, only one get actually deployed (as indicated by cloud console), but CLI reports all failing. Running deploy with --debug indicate that it tries to re-run deploy of that function until timeout is hit (lots of Retrying task index 0 followed by FirebaseError: Task index 0 failed: timed out after 300000ms.).

Downgrade to 9.3.0 helped, and build are passing fine again, but was hard to debug, running deploy without --debug just fails without any meaningful message.

I have the very same issues. Trying to upload barely changed functions and I get deployment error. It's really irritating especially when I have some quick fix to push, but google server throws error without specifically saying what's the matter. Tried last three versions of firebase-tools, but no luck.

I've been seeing this issue recently as well. It has been happening every time since upgrading firebase-tools from v9.2.0 to v9.4.0.

I've created #3150 to increase the timeout and address this. We will likely get it released in the next day or two, but in the meantime you can either downgrade to v9.3.0 or install directly from the PR branch:

npm i -g firebase/firebase-tools#mb-fn-timeout

The deployment time actually increased very quickly, it went from 5-7 minutes with 800kb to 30 minutes + with 950kb, I understand that it can take a while due to the size but I only take timeout and I don't know if it is actually an upload timeout or If there is something in the code that could be causing some kind of bottleneck, has anyone experienced this?