1# Submitting to Google Play Store
2 
3## Prerequisites
4 
51. **Google Play Console Account** - Register at [play.google.com/console](https://play.google.com/console)
62. **App Created in Console** - Create your app listing before first submission
73. **Service Account** - For automated submissions via EAS
8 
9## Service Account Setup
10 
11### 1. Create Service Account
12 
131. Go to Google Cloud Console → IAM & Admin → Service Accounts
142. Create a new service account
153. Grant the "Service Account User" role
164. Create and download a JSON key
17 
18### 2. Link to Play Console
19 
201. Go to Play Console → Setup → API access
212. Click "Link" next to your Google Cloud project
223. Under "Service accounts", click "Manage Play Console permissions"
234. Grant "Release to production" permission (or appropriate track permissions)
24 
25### 3. Configure EAS
26 
27Add the service account key path to `eas.json`:
28 
29```json
30{
31  "submit": {
32    "production": {
33      "android": {
34        "serviceAccountKeyPath": "./google-service-account.json",
35        "track": "internal"
36      }
37    }
38  }
39}
40```
41 
42Store the key file securely and add it to `.gitignore`.
43 
44## Environment Variables
45 
46For CI/CD, use environment variables instead of file paths:
47 
48```bash
49# Base64-encoded service account JSON
50EXPO_ANDROID_SERVICE_ACCOUNT_KEY_BASE64=...
51```
52 
53Or use EAS Secrets:
54 
55```bash
56eas secret:create --name GOOGLE_SERVICE_ACCOUNT --value "$(cat google-service-account.json)" --type file
57```
58 
59Then reference in `eas.json`:
60 
61```json
62{
63  "submit": {
64    "production": {
65      "android": {
66        "serviceAccountKeyPath": "@secret:GOOGLE_SERVICE_ACCOUNT"
67      }
68    }
69  }
70}
71```
72 
73## Release Tracks
74 
75Google Play uses tracks for staged rollouts:
76 
77| Track | Purpose |
78|-------|---------|
79| `internal` | Internal testing (up to 100 testers) |
80| `alpha` | Closed testing |
81| `beta` | Open testing |
82| `production` | Public release |
83 
84### Track Configuration
85 
86```json
87{
88  "submit": {
89    "production": {
90      "android": {
91        "track": "production",
92        "releaseStatus": "completed"
93      }
94    },
95    "internal": {
96      "android": {
97        "track": "internal",
98        "releaseStatus": "completed"
99      }
100    }
101  }
102}
103```
104 
105### Release Status Options
106 
107- `completed` - Immediately available on the track
108- `draft` - Upload only, release manually in Console
109- `halted` - Pause an in-progress rollout
110- `inProgress` - Staged rollout (requires `rollout` percentage)
111 
112## Staged Rollout
113 
114```json
115{
116  "submit": {
117    "production": {
118      "android": {
119        "track": "production",
120        "releaseStatus": "inProgress",
121        "rollout": 0.1
122      }
123    }
124  }
125}
126```
127 
128This releases to 10% of users. Increase via Play Console or subsequent submissions.
129 
130## Submission Commands
131 
132```bash
133# Build and submit to internal track
134eas build -p android --profile production --submit
135 
136# Submit existing build to Play Store
137eas submit -p android --latest
138 
139# Submit specific build
140eas submit -p android --id BUILD_ID
141```
142 
143## App Signing
144 
145### Google Play App Signing (Recommended)
146 
147EAS uses Google Play App Signing by default:
148 
1491. First upload: EAS creates upload key, Play Store manages signing key
1502. Play Store re-signs your app with the signing key
1513. Upload key can be reset if compromised
152 
153### Checking Signing Status
154 
155```bash
156eas credentials -p android
157```
158 
159## Version Codes
160 
161Android requires incrementing `versionCode` for each upload:
162 
163```json
164{
165  "build": {
166    "production": {
167      "autoIncrement": true
168    }
169  }
170}
171```
172 
173With `appVersionSource: "remote"`, EAS tracks version codes automatically.
174 
175## First Submission Checklist
176 
177Before your first Play Store submission:
178 
179- [ ] Create app in Google Play Console
180- [ ] Complete app content declaration (privacy policy, ads, etc.)
181- [ ] Set up store listing (title, description, screenshots)
182- [ ] Complete content rating questionnaire
183- [ ] Set up pricing and distribution
184- [ ] Create service account with proper permissions
185- [ ] Configure `eas.json` with service account path
186 
187## Common Issues
188 
189### "App not found"
190 
191The app must exist in Play Console before EAS can submit. Create it manually first.
192 
193### "Version code already used"
194 
195Increment `versionCode` in `app.json` or use `autoIncrement: true` in `eas.json`.
196 
197### "Service account lacks permission"
198 
199Ensure the service account has "Release to production" permission in Play Console → API access.
200 
201### "APK not acceptable"
202 
203Play Store requires AAB (Android App Bundle) for new apps:
204 
205```json
206{
207  "build": {
208    "production": {
209      "android": {
210        "buildType": "app-bundle"
211      }
212    }
213  }
214}
215```
216 
217## Internal Testing Distribution
218 
219For quick internal distribution without Play Store:
220 
221```bash
222# Build with internal distribution
223eas build -p android --profile development
224 
225# Share the APK link with testers
226```
227 
228Or use EAS Update for OTA updates to existing installs.
229 
230## Monitoring Submissions
231 
232```bash
233# Check submission status
234eas submit:list -p android
235 
236# View specific submission
237eas submit:view SUBMISSION_ID
238```
239 
240## Tips
241 
242- Start with `internal` track for testing before production
243- Use staged rollouts for production releases
244- Keep service account key secure - never commit to git
245- Set up Play Console notifications for review status
246- Pre-launch reports in Play Console catch issues before review
247