How to Publish an Expo App on Google Play
Expo's EAS (Expo Application Services) makes publishing to Google Play remarkably straightforward. You can build Android App Bundles in the cloud without touching Android Studio, manage signing keys automatically, and submit directly to Play Console from the command line. This guide walks through the complete process from configuration to going live.
Prerequisites
- An Expo account (free at expo.dev)
- A Google Play Developer account ($25 one-time fee)
- EAS CLI installed globally (npm install -g eas-cli)
- Your Expo app configured with a unique package name
- app.json with android configuration section filled in
Step-by-Step Build Process
Configure app.json for Android
Set `expo.android.package` (e.g., 'com.yourcompany.appname'). Set `expo.android.versionCode` (integer, increment for each release). Add required permissions in `expo.android.permissions` array.
Configure EAS Build profiles
Run `eas build:configure` if you haven't already. In eas.json, the production profile should have `"android": { "buildType": "app-bundle" }` to generate AAB format required by Google Play.
Run the cloud build
Execute `eas build --platform android --profile production`. EAS will generate and manage your upload keystore automatically. The build produces an .aab file ready for Google Play.
Verify the build
Download the AAB from the EAS dashboard. You can use Google's `bundletool` to test locally: `bundletool build-apks --bundle=app.aab --output=app.apks --local-testing`.
Code Signing & Certificates
EAS-managed keystore (recommended)
EAS generates and securely stores your upload keystore automatically. This is the recommended approach for most developers. You can download a backup of the keystore from the Expo dashboard under project credentials.
Play App Signing integration
When you upload your first AAB, Google Play will manage the app signing key. EAS uses a separate upload key. If you ever lose the upload key, Google can reset it — but always keep backups via `eas credentials`.
Store Submission Steps
Create the app in Google Play Console
In Play Console, click 'Create app'. Set the app name, default language, app/game type, and free/paid status.
Complete the store listing
Add short description (80 chars), full description (4000 chars), app icon (512x512), feature graphic (1024x500), and at least 2 phone screenshots.
Submit using EAS Submit
Run `eas submit --platform android`. You'll need a Google Play service account JSON key for authentication. EAS guides you through creating one in the Google Cloud Console and linking it to Play Console.
Complete compliance requirements
Fill in the content rating questionnaire, data safety section, and target audience declaration in Play Console. Set up pricing and country distribution.
Roll out to production
Once all sections are complete and the build is processed, roll out to production. First-time app reviews typically take 1-7 days.
Common Rejection Reasons & Fixes
Data Safety Form incomplete
Google requires detailed data safety declarations. Expo apps using expo-analytics, expo-notifications, or any networking libraries collect data. Declare all data types honestly in the Data Safety section.
Target API level too low
Google requires targeting recent API levels. Update `expo.android.targetSdkVersion` in app.json or upgrade your Expo SDK version which automatically targets appropriate API levels.
App crashes on specific Android versions
Test on Android emulators running API 28+ (Android 9+). Expo apps occasionally have issues with older Android versions due to missing polyfills. Check crash reports in Play Console's Android Vitals.
Missing privacy policy
All apps must have a privacy policy URL set in both Play Console and within the app. Add a link in your app's settings screen and in the store listing.
Pro Tips
- Use `eas build --auto-submit` to combine build and Play Store submission in one command
- Set up internal testing tracks first — they don't require full store listing completion
- Use EAS Update for over-the-air JavaScript updates without going through Play Store review
- Monitor Android Vitals in Play Console for crash rate and ANR metrics
- Consider staged rollouts (e.g., 20% of users first) for major updates
Skip the hassle. Let us handle it.
Publishing a Expo app on the Google Play (Android) involves dozens of steps, certificates, and potential rejection pitfalls. Our team handles the entire process for you — from build configuration to store approval.