How to Fix Firebase Deployment Error Quickly and Easily

To fix a firebase deployment error, first check your firebase.json and .firebaserc files for correct configuration. Also, ensure you are logged in with firebase login and your project ID matches the Firebase console. Running firebase deploy --only hosting after fixing these usually resolves the issue.

Why This Happens

Firebase deployment errors often happen because of misconfigured files, wrong project selection, or missing login credentials. For example, if your firebase.json file has incorrect paths or your CLI is not logged into the right Firebase account, deployment will fail.

json

{
  "hosting": {
    "public": "wrong-folder",
    "ignore": ["firebase.json", "**/.*", "**/node_modules/**"]
  }
}

Output

Error: Hosting public directory 'wrong-folder' does not exist.

The Fix

Update your firebase.json to point to the correct folder where your built files are located, usually public or build. Also, run firebase login to ensure you are authenticated, and use firebase use <project-id> to select the right project. Then deploy again with firebase deploy.

json

{
  "hosting": {
    "public": "public",
    "ignore": ["firebase.json", "**/.*", "**/node_modules/**"]
  }
}

Output

✔  Deploy complete!
Project Console: https://console.firebase.google.com/project/your-project-id/overview

Prevention

Always verify your firebase.json paths before deploying. Use firebase projects:list to confirm your project ID. Keep your Firebase CLI updated and run firebase login if you switch accounts. Automate checks with scripts or CI/CD pipelines to catch errors early.

Related Errors

• Authentication errors: Fix by running firebase login again.
• Permission denied: Check your Firebase project roles and permissions.
• Build folder missing: Run your build command before deploying.

Key Takeaways

Check and correct your firebase.json public folder path before deploying.

Always log in with firebase login and select the right project with firebase use.

Keep Firebase CLI updated to avoid compatibility issues.

Run your build process before deploying to ensure files exist.

Use automated checks to catch deployment issues early.