Prepare the store application and credentials
Follow the current Android submission guide for Google Play prerequisites, service-account access and first-time submission options. Do not assume an older tutorial's first-upload restriction or Console path still applies unchanged.
Keep the service-account key out of app assets and public source. It is a privileged submission credential, not client configuration.
Submit the intended build
An illustrative command is:
eas submit --platform android
Select the correct build and submission profile. For automation, pin profile and environment deliberately rather than relying on the most recent build belonging to another branch.
Separate submission states
| State | Meaning |
|---|---|
| EAS build complete | Artifact was produced |
| Submission complete | Upload/API operation completed |
| Draft release | Further Console action may be required |
| In review | Google is evaluating the submitted changes |
| Rolled out | Release availability follows track and country settings |
The Play release documentation governs the store-side process. A successful API response is not a publishing guarantee.
Match upload and app-signing identities
Use the Expo credentials guidance and the app's Play signing setup. Do not generate a new keystore for an existing app merely because the current CI environment cannot find its credentials.
Complete declarations and test delivery
Review app access, Data safety, content rating, target API and account-specific requirements. Install the Play-delivered test build to verify sign-in, billing, native modules and update behavior.
APKLint's bundle and release tools can support pre-upload inspection. They cannot read your private release status or approve the submission. Retain the EAS build/submission identifiers and the actual Play track outcome as separate release evidence.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
