Firebase Deploy Failed (Functions and Hosting)

How to fix it

Try these in order — the most common fix is first.

1. 1. Verify billing

   Copy steps
   1. Firebase console > Usage and billing: confirm Blaze
   2. In Google Cloud console confirm the billing account is open and linked
   Did this fix it? Yes No

2. 2. Enable APIs and check permissions

   Copy steps
   1. Enable Cloud Build and Artifact Registry APIs
   2. Check the Cloud Build and compute service accounts have required roles
   Did this fix it? Yes No

3. 3. Get the real error

   Copy steps
   1. Run firebase deploy --only functions --debug
   2. Look in Cloud Build logs for the failing step
   Did this fix it? Yes No

4. 4. Retry cleanly

   1. Run npm install and test locally with the emulator, then redeploy a single function with --only functions:name
   Did this fix it? Yes No

Symptoms

firebase deploy fails with build errors, 'Failed to create function' or build status errors.

Why it happens

• Project on Spark or billing account closed/unlinked
• Cloud Build or Artifact Registry API disabled
• Build service account lacks permissions
• Transient build failures or timeouts
• Mismatched Node runtime or code errors

This guide also covers

• firebase deploy failed
• firebase deploy functions error
• firebase functions build failed

Other Firebase errors

• Firestore Missing or Insufficient Permissions (permission-denied)
• Firebase auth/invalid-api-key Error
• Firebase auth/network-request-failed Error
• Firebase auth/too-many-requests Error
• Firebase auth/operation-not-allowed Error
• Firestore Quota Exceeded (resource-exhausted)
• Firebase Unexpected Bill on Blaze Plan
• Firebase Cloud Messaging Notifications Not Received