Expo Android push fails because google-services.json is missing
"google-services.json" is missing for firebaseShort answer
Android push in Expo goes through Firebase Cloud Messaging, which needs two separate things: the google-services.json file inside the app, pointed to by android.googleServicesFile, and a service account key uploaded to Expo for sending. If either is missing, the app never gets a push token or the send fails. Add both, then make a new build.
Fix it fast
1Find out which cause you have
Check whether your app config points at the file, and whether the file exists at that path.
grep -n "googleServicesFile" app.json app.config.* 2>/dev/null ls -l google-services.json2Match what you see, then jump to its fix
What does the error look like?
"google-services.json" is missing for firebase
Cause 1 of 2
The app config does not point to google-services.json
1Check
Expo's guide says the file is required for the Android app to be registered with FCM. You download it from the Firebase console and place it in the project root.
grep -n "googleServicesFile" app.json app.config.* 2>/dev/null2Fix
Download google-services.json from your Firebase project settings, put it in the project root, and set its path under android in app.json. The file only holds public identifiers, so Expo says you may commit it.
{
"expo": {
"android": {
"googleServicesFile": "./google-services.json"
}
}
}3Verify
Create a new build; a config change needs one.
eas build --platform android --profile developmentConfirmed by raw.githubusercontent.com
Cause 2 of 2
The FCM service account key was never uploaded to Expo
1Check
Sending needs a Google service account key. In the Firebase console, open Settings > Service accounts and see whether you have generated a private key and uploaded it.
eas credentials2Fix
Generate a new private key in Firebase, then upload it with EAS CLI: run eas credentials, choose Android, the build profile, and Google Service Account. You can also upload it on the Credentials page of expo.dev. Keep the JSON file out of version control.
eas credentials3Verify
Send a test push to the Expo push token and check it arrives on the device.
# send a test push to the device and check it arrivesConfirmed by raw.githubusercontent.com
How do I stop it coming back?
- Add the expo-notifications plugin to the plugins array of your app config.
- Test on a development build or an emulator with Google Play services.
- Never commit the service account JSON; the google-services.json file is the one that is safe to commit.
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:
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- 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.
Related fixes
Mobile 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
FirebaseInstanceIdService and FirebaseInstanceId.getToken() no longer work
Deprecation warning on FirebaseInstanceId.getInstance().getToken()
Move token handling into a class that extends FirebaseMessagingService and override onNewToken, which runs when a token is first created and whenever it changes.
2 causes, each with a fixMobile apps
The Google Services plugin cannot find google-services.json in an Android app
File google-services.json is missing from module root folder. The Google Services Plugin cannot function without it.
The Google Services plugin looks for google-services.json in the app module folder, or in a build-type folder under src.
3 causes, each with a fixMobile apps
Logcat warns that FCM has no default notification channel in AndroidManifest
Notification does not appear on Android 8 and later
This is a warning, not a crash.
3 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 phone sign-in fails with status 17028 and play_integrity_token
SMS verification code request failed: unknown status code: 17028 Invalid request fields in play_integrity_token
Firebase checks the app with Play Integrity before sending an SMS, and that check needs your SHA-256 fingerprint.
3 causes, each with a fix