Play Store Deployment
Build, submit, and publish your mobile app to the Google Play Store with EAS Build and EAS Submit.
Play Store Deployment
This guide covers building your Android app with EAS, submitting to Google Play, and completing the review process.
Prerequisites
- Google Play Console account — $25 one-time fee at play.google.com/console
- App created in Google Play Console
- EAS CLI installed and logged in
1. Prepare Your App
Update app.json before your first production build:
{
"expo": {
"name": "Your App Name",
"slug": "your-app-slug",
"version": "1.0.0",
"android": {
"package": "com.yourcompany.yourapp",
"versionCode": 1,
"adaptiveIcon": {
"foregroundImage": "./assets/adaptive-icon.png",
"backgroundColor": "#FFFFFF"
}
}
}
}Important: The
packagename cannot be changed after publishing to the Play Store. Choose carefully.
2. Build with EAS
eas build --platform android --profile productionEAS generates and manages the upload key automatically on first build. For the app signing key, use Google Play App Signing (recommended) which lets Google manage the final signing key.
The build produces an AAB (Android App Bundle) file. Builds take approximately 10-15 minutes.
3. Submit to Google Play
eas submit --platform androidFor the first submission, you need a Google Service Account JSON key:
- Go to Google Play Console > Setup > API access
- Create a new service account or link an existing one
- Grant the service account Release manager permissions
- Download the JSON key
- Provide the path when EAS Submit prompts for it
Configure Submission Track
Set the submission track in eas.json:
{
"submit": {
"production": {
"android": {
"track": "internal",
"serviceAccountKeyPath": "./google-service-account.json"
}
}
}
}| Track | Description |
|---|---|
internal | Internal testing (up to 100 testers) |
alpha | Closed testing |
beta | Open testing |
production | Public release |
Tip: Start with
internalfor testing, then promote toproductionin the Play Console.
4. Complete the Play Console Setup
In Google Play Console, complete the required information:
Store Listing
- App title and description — Short description (80 chars) and full description (4000 chars)
- Screenshots — At least 2 phone screenshots, plus tablet if applicable
- Feature graphic — 1024x500 PNG or JPEG
- App icon — 512x512 PNG (32-bit, with alpha)
Content Rating
Complete the content rating questionnaire. This is required before you can publish.
Privacy Policy
Add a privacy policy URL. Required for all apps.
Data Safety
Complete the data safety form declaring what data your app collects:
- Email addresses (for authentication)
- User identifiers (for account management)
- Crash logs (if using error reporting)
Target Audience
Declare if the app is designed for children. If not, select "Not designed for children."
Google Play Review Process
Google Play reviews are typically faster than Apple — usually a few hours to 1-2 days. First submissions may take longer.
Key requirements:
- Content rating questionnaire completed
- Privacy policy URL provided
- Data safety form completed
- Target audience declared
- All store listing assets uploaded
Version Bumping
For each new release, increment the version and version code in app.json:
{
"expo": {
"version": "1.1.0",
"android": {
"versionCode": 2
}
}
}The version is displayed to users. The versionCode must be strictly increasing with each submission.
Signing Key Management
EAS manages your upload key automatically. If you need to manage keys manually:
eas credentials --platform androidThis lets you view, download, or replace your signing credentials.