flutterfire configure says the directory is not a Flutter application project
FlutterAppRequiredException: The current directory does not appear to be a Flutter application project.Short answer
FlutterFire CLI looks for a pubspec.yaml in the current directory and then checks that it describes a Flutter app. If the file is missing, or the project is not a Flutter app (for example a plugin package), it throws FlutterAppRequiredException. Run the command from the app's root folder.
Fix it fast
1Find out which cause you have
Print the folder you are in and check that pubspec.yaml is there.
pwd ls pubspec.yaml2Match what you see, then jump to its fix
What does the error look like?
FlutterAppRequiredException: The current directory does not appear to be a Flutter application project.
Cause 1 of 3
The command runs outside the project root
1Check
The CLI throws this exception when no pubspec.yaml exists in the directory it is run from. A shell opened in your home folder or in ios/ or android/ does this.
pwd
ls pubspec.yaml2Fix
Change into the Flutter project root, then run the command. Firebase's guide says to run it from your Flutter project directory.
cd path/to/my_app
flutterfire configure3Verify
The command now lists your Firebase projects.
flutterfire configureConfirmed by firebase.google.com
Cause 2 of 3
pubspec.yaml does not depend on the Flutter SDK
1Check
The CLI treats a package as a Flutter app only when it is a Flutter package. Open pubspec.yaml and look for the flutter SDK dependency.
sed -n '1,40p' pubspec.yaml2Fix
Add the Flutter SDK dependency under dependencies, then fetch packages.
# pubspec.yaml
dependencies:
flutter:
sdk: flutter
# then
flutter pub get3Verify
Run the command again from the same folder.
flutterfire configureConfirmed by raw.githubusercontent.com
Cause 3 of 3
The project is a plugin, not an app
1Check
The CLI source says a Flutter app must not have a Flutter plugin definition in its pubspec.yaml. A plugin package therefore fails the check.
grep -n "plugin:" pubspec.yaml2Fix
Run the command in an app project, not in the plugin package itself.
cd path/to/my_app
flutterfire configure3Verify
The command starts the configuration without the exception.
flutterfire configureConfirmed by raw.githubusercontent.com
How do I stop it coming back?
- Keep a terminal open at the project root when you set up Firebase.
- Install the CLI once with dart pub global activate flutterfire_cli; it can be run from any directory, but configure must run in the app folder.
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:
- SessionBirdAn omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
- Spotless LaundryAn on-demand laundry app: Flutter on a Laravel back end, with Firebase for live updates.
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
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 fixMobile apps
Firestore returns permission-denied: Missing or insufficient permissions
FirebaseError: [code=permission-denied]: Missing or insufficient permissions.
Firestore rejected the request because your security rules, or App Check enforcement, did not allow it.
4 causes, each with a fixMobile apps
Flutter Android: Failed to load FirebaseOptions from resource
Failed to load FirebaseOptions from resource. Check that you have defined values.xml correctly.
On Android, Firebase reads its settings from a values.xml file that the Google services Gradle plugin builds from google-services.json.
4 causes, each with a fixMobile apps
Flutter: FirebaseException No AppCheckProvider installed
com.google.firebase.FirebaseException: No AppCheckProvider installed
Firebase App Check needs a provider chosen in your Dart code before other Firebase calls run.
3 causes, each with a fixMobile apps
FirebaseMessaging.getAPNSToken() returns null on iOS
FirebaseMessaging.instance.getAPNSToken() returns null
getAPNSToken() gives null when iOS has not handed the app an APNs token yet or never will.
4 causes, each with a fix