David Griffin
David Griffin

Reputation: 97

Firebase Extension - Stripe Payments keeps failing to deploy resources

For the past hour I've been trying to install the Firebase Extension for Stripe Payments, and unfortunately it keeps failing to deploy the required resources. May someone might be able to help me debug this and install the extension successfully.

I've tried installing it via the Firebase GUI. as well as via the Firebase CLI, same errors. After attempting to re-install, the extension claims its installed, but unfortunately the functions are still flagged with the error: Function deployment failed. Try again. - And I don't know how to manually deploy, other than deploying the entire extension via the CLI, which initially fails with the error.

Upon re-deploying, it appears successful (similar to re-installing in the GUI) but yet again, the functions required are flagged with an error in the GUI as Function deployment failed. Try...

Error:

Extensions deploy had errors:

Error: Extensions deployment failed.

enter image description here

enter image description here

enter image description here

Upvotes: 2

Views: 370

Answers (3)

Rustem Bekmukhametov
Rustem Bekmukhametov

Reputation: 62

On screenshot above, the value of 30 appears to be pulled from the previous successful deployment, whereas the error of >32 applies to the latest deployment attempt that has failed due to quota. As to the quota itself, the answer above from Joe and Iman provides more clues on reasons and a workaround.

Upvotes: 0

Joe Hanley
Joe Hanley

Reputation: 216

Firebaser here

There's a limit on Cloud Functions quota based on multiple criteria that are checked behind the scenes. Eventually these limits might increase as usage continues. As an immediate workaround, try setting maxInstances in the advanced settings dropdown to <32 instances.

Upvotes: 4

David Griffin
David Griffin

Reputation: 97

Unfortunately I had to discover that there is an issue with Firebase at the current point in time, which means that extensions and functions deployed to europe-west-3 run into this error, but not functions deployed to us-central-1

This happens on legacy projects as well as brand-new projects.

Therefore, the current "Solution" to this problem, is to install the extension, with us-central-1 as the location from where the functions are executed.

Upvotes: 0

Related Questions