Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

firebase projects:create or flutterfire configure says 'Failed to create project'

ErrorError: Failed to create project. See firebase-debug.log for more info.

Short answer

A Firebase project is a Google Cloud project, so creation fails on the same rules: the ID must be 6 to 30 lowercase characters and never used before (deleted projects count), your account must be allowed to create projects, and you must be under the project limit. Read firebase-debug.log, then check these three.

  • Applies to firebase-tools (current), Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open firebase-debug.log, the file the error message names, and read the last error lines. They carry the real reason that the one-line message hides.

    tail -n 40 firebase-debug.log
  2. 2Match what you see, then jump to its fix

    1. 1the log complains about the project IDThe project ID is invalid or was used beforeFix
    2. 2the log mentions a limit or quotaThe account has reached its project limitFix
    3. 3the log mentions permission deniedThe logged-in Google account may not create projectsFix

What does the error look like?

  • Error: Failed to create project. See firebase-debug.log for more info.

Cause 1 of 3

The project ID is invalid or was used before

1Check

The ID must be 6 to 30 characters, only lowercase letters, numbers and hyphens, start with a letter, not end with a hyphen, and not contain restricted strings such as google. It also must never have been used, and that includes deleted projects.

echo -n "my-app-prod" | wc -c

2Fix

Pick a new, more specific ID, for example with a short suffix, and create again.

firebase projects:create

3Verify

The command finishes and reports the new project.

firebase projects:create

Confirmed by docs.cloud.google.com

Did this fix it?

Cause 2 of 3

The account has reached its project limit

1Check

The number of projects a user can create is limited, and a project that was deleted keeps counting until it is fully removed, which takes 30 days.

firebase projects:create --help

2Fix

Reuse or shut down an unused project, or request a project limit increase. Linking a Cloud Billing account in good standing can raise the quota.

firebase projects:create --help

3Verify

Create the project again, or configure the app against an existing one.

firebase projects:create

Confirmed by firebase.google.com

Did this fix it?

Cause 3 of 3

The logged-in Google account may not create projects

1Check

Creating a project needs the resourcemanager.projects.create permission, which roles such as Project Creator include. In a company account an administrator may have removed it, or you may be signed in with the wrong account.

firebase login

2Fix

Sign in with an account that has the permission, or ask the organisation admin for the Project Creator role.

firebase login

3Verify

Run the create command again.

firebase projects:create

Confirmed by docs.cloud.google.com

Did this fix it?

How do I stop it coming back?

  • Decide the project ID once, check it against the rules, and keep it in your setup notes.
  • Delete test projects you no longer need only after copying data you need, as they count toward quota for 30 days.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

FCM says the token is not found when you send a push

UNREGISTERED

The FCM HTTP v1 API returns UNREGISTERED with HTTP 404 when the app instance behind a token is gone: the app was uninstalled, the token expired, the client unregistered, or the token you pass is empty.

2 causes, each with a fix

Mobile apps

The iOS push arrives from FCM but plays no sound

A custom sound name in the payload is ignored and nothing plays

iOS plays a sound for a remote notification only when the aps payload has a sound key and the app is allowed to play sounds.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.