Build the app bundle through the supported workflow
The current React Native guide documents:
npx react-native build-android --mode=release
In that documented workflow the command invokes bundleRelease and produces an AAB. Check your installed React Native/CLI version and flavor configuration rather than assuming every older project accepts identical options.
Verify release identity
Confirm application ID, version code, upload keystore and production environment. Keep secrets in appropriate build/CI storage, not committed Gradle properties or JavaScript constants.
Test the packaged app without Metro and verify all required assets and native modules are present.
Apply current Play requirements
The target API page is the source for current form-factor-specific requirements. The release guide covers tracks and submission steps.
Complete declarations based on the actual SDKs and behavior, not only your own JavaScript code. Native advertising, analytics and authentication libraries can affect disclosures.
Test through the intended track
| Check | Why it matters |
|---|---|
| Sign-in | Play-delivered certificate |
| Billing | Store test environment |
| Native module startup | Release linking/code generation |
| Offline launch | Packaged JS/assets |
| Update from prior release | Data and identity compatibility |
Use a dedicated test environment and avoid destructive uninstall workarounds that conceal upgrade problems.
Archive the release inputs
Keep lockfiles, source revision, native build configuration, AAB hash and mappings/symbols. APKLint's React Native, bundle and release-checklist tools can support artifact inspection, but they do not validate private Console settings or execute the application. Production readiness requires the real delivered-build tests and review outcome.
Verify the candidate before uploading its bundle
For a flavored project, record the intended package identity, production environment and release task. Inspect the generated AAB's version and associate it with the source revision and dependency lockfiles. A successful build can still contain a staging endpoint or an older JavaScript entry configuration. Keep the selected artifact's digest so later tests can identify the same candidate.
The React Native publishing guide documents its app-bundle command and release bundling behavior. Check the installed CLI version when adapting the command to custom variants. An APK assemble task and an AAB bundle task serve different delivery purposes.
Validate the Play-delivered application as a distinct stage
Install through the intended test track with an eligible account. Verify the version actually installed, then test sign-in and another native integration under the store-delivered certificate and packaging. Keep a local APK test as supporting evidence without treating it as identical to Play delivery. If the application supports downloadable updates, record the update channel and executed bundle identity during the test. Otherwise a later JavaScript update can change behavior without changing the native artifact whose results were originally recorded.
Stop Metro and exercise a route containing local assets, an offline path and a native module. Update over the intended previous release using synthetic data and verify migration behavior. If a test device carries a higher version code from another track, account for that state before diagnosing a failed or missing update.
Review the actual native SDKs as well as JavaScript dependencies when preparing disclosures and reviewer access. An advertising, analytics or authentication module can contribute data behavior that the application's own JavaScript does not visibly implement. Confirm that app-access instructions work from a fresh reviewer-like session and that any test credentials are handled through the authorized console flow.
Retain mappings, source maps and native symbols with the candidate and verify a controlled diagnostic event where appropriate. Distinguish upload acceptance, policy review, rollout state and user availability in the release record. A package checker can support artifact inspection but cannot certify account-specific console requirements or distribution success. Expand availability only on the basis of the actual delivered-build tests and the release workflow's observed state.
Sources and further reading
- React Native: Publishing to Google Play Store
- Google Play: Prepare and roll out a release
- Google Play: Target API level requirements
Reference review: 29 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
