How to publish a React Native (Expo) app to Google Play
Updated
To publish a React Native app built with Expo to Google Play, build a signed Android App Bundle with EAS Build, create the app in the Play Console, give Expo a Google service account key, then submit the build to a testing track and promote it to production. Bappfy runs these steps for you on your own Expo account.
The steps
- 1
Build the .aab with EAS
EAS Build signs the bundle with a keystore stored on your Expo account. Keep that key: Google ties your app's updates to it.
- 2
Create the app in the Play Console
Use the same package name as in your app config. It can't change later.
- 3
Create a service account
In Google Cloud, create a service account with a JSON key, then invite its email in the Play Console (Users and permissions) with release rights.
- 4
Submit to a testing track
EAS Submit uploads the build to a track such as internal testing. A draft release lets you check everything before rolling out.
- 5
Pass the closed test if needed, then go to production
New personal accounts need 12 testers for 14 days in a closed test first. Then promote the release and send it for review.
Doing it from Bappfy
In Publish, choose Android .aab, click Connect Google Play, choose your service account JSON key, then tick Also send to Google Play. Bappfy builds the app on your Expo account and uploads it to internal testing as a draft; the key is stored on your Expo account, not by Bappfy.
Some accounts may still need the very first upload done by hand in the Play Console; after that, every build goes up automatically.
Frequently asked questions
- Do I need eas.json?
- With Bappfy it's generated for you. In a hand-made Expo project, eas.json holds the build and submit profiles.
- Which track should I use first?
- Internal testing: it's available within minutes to your testers and doesn't need the full review.