eas submit fails against Google Play because the service account lacks access
Google Service Account Keys cannot be set up in --non-interactive mode.Short answer
eas submit uploads through a Google service account. It is refused when that account is not invited in Play Console, lacks release and store permissions, belongs to a project without the Google Play Android Developer API enabled, or its key is assigned to another app. Check each in order and fix the one that is wrong.
Fix it fast
1Find out which cause you have
Find out which service account EAS uses for this app, and which app id it submits. Then compare them with what Play Console shows under Users and permissions.
eas credentials --platform android grep -n "package" app.json2Match what you see, then jump to its fix
- 1
The key is valid and the upload still gets a permissions refusal.The service account is not invited, or lacks release permissionsFix - 2
The account looks right in Play Console but calls to the Google API are refused.The Google Play Android Developer API is not enabled for the key's projectFix - 3
The key works for one app and fails for another in the same account.The key is assigned to a different Android appFix - 4
Google Service Account Keys cannot be set up in --non-interactive mode.A non-interactive run has no key assignedFix
- 1
What does the error look like?
Google Service Account Keys cannot be set up in --non-interactive mode.eas submit to Google Play ends with a permissions error for the service account
Cause 1 of 4
The service account is not invited, or lacks release permissions
1Check
The Expo service-account guide has you invite the account's email in Play Console under Users and permissions, pick the app, and grant app access, draft apps, releases (release to production, testing tracks, manage testing tracks) and store presence. Open the Play Console page and look for the account's email in the list.
# compare the service account email in Play Console with the key EAS holds
eas credentials --platform android2Fix
Invite the service account email and grant the permissions the guide lists for the app, then submit again. You do not need Admin or the financial permissions.
eas submit --platform android --latest3Verify
The submit finishes and a release appears on the track.
eas submit --platform android --latestConfirmed by github.com
Cause 2 of 4
The Google Play Android Developer API is not enabled for the key's project
1Check
Both the Expo guide and the Google Play Developer API guide list enabling the Google Play Android Developer API in the Google Cloud project that owns the service account as a required step.
eas credentials --platform android2Fix
In Google Cloud Console, select that project and click Enable on the Google Play Android Developer API page.
# Google Cloud Console > APIs & Services > Library > Google Play Android Developer API > Enable3Verify
Run the submit again.
eas submit --platform android --latestConfirmed by developers.google.com
Cause 3 of 4
The key is assigned to a different Android app
1Check
The Expo submit docs say each service account key is assigned to one Android application identifier in EAS.
eas credentials --platform android2Fix
Assign a key to this app in EAS credentials, and make sure that service account was invited for this app in Play Console. For CI, point to a key file on the build machine as the docs describe.
eas credentials --platform android3Verify
Submit this app again.
eas submit --platform android --latestConfirmed by docs.expo.dev
Cause 4 of 4
A non-interactive run has no key assigned
1Check
In CI the CLI cannot prompt for a key. The Expo docs say to assign a key to the app beforehand, or give a path to a key file on the CI machine.
eas submit --platform android --latest --non-interactive2Fix
Assign the key once from your computer, or write serviceAccountKeyPath in the submit profile of eas.json.
eas credentials --platform android3Verify
Re-run the CI job.
eas submit --platform android --latest --non-interactiveConfirmed by docs.expo.dev
How do I stop it coming back?
- Create one service account per app, or document which apps share one, and invite it from the start.
- Keep the JSON key outside version control and load it from your CI secret store.
- Run eas submit once from your computer before wiring it into CI.
- Record the required permission list in your release checklist.
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
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fix