Create an explicit preview profile
The Expo APK guide documents this configuration:
{
"build": {
"preview": {
"android": { "buildType": "apk" }
}
}
}
This is an eas.json fragment. Keep production and preview settings separate so a test artifact is not accidentally submitted as the store release.
Build the selected profile
eas build -p android --profile preview
Use the project's installed/supported EAS CLI workflow. Confirm package ID, environment and credentials before starting a build that uses remote infrastructure.
Distinguish preview from development client
A development client can require the development server for its intended workflow. A standalone preview/release APK should be tested according to its own configuration.
| Build purpose | Test expectation |
|---|---|
| Development client | Developer tooling and server workflow |
| Standalone preview | Packaged app launches independently |
| Production store | App bundle and Play distribution checks |
Inspect credentials and updates
The Expo credentials guide explains managed signing material. A different key can prevent installing the APK as an update over another build with the same package.
Do not uninstall a user's real app merely to force a test installation without considering data loss. Use a dedicated test device or distinct development package where appropriate.
Test the actual native configuration
A change requiring native code is not automatically covered by a JavaScript-only update. Build a new native artifact when the integration requires it.
APKLint's React Native Analyzer and signing tools can help inspect the APK's framework and identity metadata. They cannot confirm the EAS account configuration or run the app. Keep the EAS build identifier and a standalone-device test with the artifact.
Choose whether the tester needs a standalone preview
Suppose a tester needs to install the app from a build link and evaluate it without a developer running Metro. Select a profile that produces the intended standalone APK, then inspect inherited profile settings for development-client behavior, environment and package identity. A profile named preview can still inherit configuration that does not match the tester's expectations.
The Expo APK guide documents the buildType setting and installation workflow. The JSON above is a minimal profile example, not a complete production policy. Preserve other required project settings and use the profile name explicitly in the build command.
Associate the downloaded file with its EAS build
Record the EAS build identifier, source revision, selected profile and artifact digest. Confirm the app's package ID and certificate before installing it over another test release. A preview signed with a different key can legitimately fail to replace an existing installation with the same package name.
Use a disposable test installation or an intentionally separate development identity when coexistence is required. Do not erase a user's production data merely to overcome a signing mismatch. If the purpose is to test updates, preserve the prior installation and correct the identity relationship instead. Keep the previous preview's certificate record available for that comparison.
Launch the downloaded APK with the development server stopped and exercise images, navigation and a native feature. After a change that adds native code or alters native configuration, create a compatible new native build; a JavaScript update cannot supply a missing Android library. Verify update-channel and runtime compatibility settings according to the project's supported Expo workflow before assuming every published update applies to every preview.
Keep the distinction between a preview, a development client and a store candidate visible in the release notes for testers. The expected startup path and credentials can differ. APK inspection supports identity and packaging review, while the installed-device test establishes whether the tester can use the chosen build independently and whether its native features match the code being evaluated.
Sources and further reading
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
