firebase projects:create or flutterfire configure says 'Failed to create project'
Error: 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.
Fix it fast
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.log2Match what you see, then jump to its fix
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 -c2Fix
Pick a new, more specific ID, for example with a short suffix, and create again.
firebase projects:create3Verify
The command finishes and reports the new project.
firebase projects:createConfirmed by docs.cloud.google.com
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 --help2Fix
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 --help3Verify
Create the project again, or configure the app against an existing one.
firebase projects:createConfirmed by firebase.google.com
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 login2Fix
Sign in with an account that has the permission, or ask the organisation admin for the Project Creator role.
firebase login3Verify
Run the create command again.
firebase projects:createConfirmed by docs.cloud.google.com
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:
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- SessionBirdAn omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.
Related fixes
Mobile apps
flutterfire configure fails with FirebaseCommandException from the Firebase CLI
FirebaseCommandException: An error occured on the Firebase CLI when attempting to run a command.
flutterfire configure runs the Firebase CLI underneath, so any CLI failure surfaces as FirebaseCommandException.
4 causes, each with a fixMobile apps
FCM rejects the message with INVALID_ARGUMENT
HTTP 400 from fcm.googleapis.com/v1/projects/PROJECT_ID/messages:send
INVALID_ARGUMENT is HTTP 400: FCM did not accept the request parameters.
3 causes, each with a fixMobile apps
Push sending broke because the server still uses the legacy FCM API
Console notice that the legacy Firebase Cloud Messaging API is deprecated
Sends that still use the legacy FCM API (a server key in the Authorization header) or old Admin SDK methods need to move to the HTTP v1 API.
3 causes, each with a fixMobile 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 fixMobile 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 fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fix