IllegalStateException: Default FirebaseApp is not initialized in this process
Firebase couldn’t initialise because google-services.json or the Google Services Gradle plugin is missing/misapplied, or initialisation happens in another process.
Seen on:
Android
Meaning
The google-services plugin turns google-services.json into resources Firebase reads at startup. Missing plugin, JSON in the wrong folder, package name mismatch, or using Firebase in a separate process causes this.
Common causes
- com.google.gms.google-services plugin not applied
- google-services.json missing or in the wrong module folder
- Package name not in the JSON
- Using Firebase in a secondary process without initializeApp
⚡ Quick fix
- Apply the plugin in the app module
- Put google-services.json in app/
- Call FirebaseApp.initializeApp(context) in multi-process setups
Detailed fix by platform
Gradle
- kotlin
plugins { id("com.android.application") id("com.google.gms.google-services") }
How to diagnose
- Plugin — Applied?
- File — app/google-services.json, package names inside
- Process — Which process crashed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- adb server version doesn't match adb server version (41) doesn't match this client (39); killing...
- ApiException: 10 Google Sign-In: com.google.android.gms.common.api.ApiException: 10 (DEVELOPER_ERROR)
- auth/invalid-credential Firebase Auth: auth/invalid-credential (auth/wrong-password, auth/user-not-found, auth/invalid-login-credentials)
Most viewed in Android
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026