Flutter, React Native & Unity

Build an Expo Android APK for Device Testing with EAS

EAS Build normally targets an Android App Bundle for store distribution. To install a build directly on a device or emulator, configure an APK-producing profile instead of renaming an AAB file.

By Updated 2 min read

Create an explicit preview profile

The Expo APK guide documents this configuration:

JSON · REFERENCE EXAMPLE
{
  "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

BASH · REFERENCE EXAMPLE
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.

Sources and further reading

  1. Expo: Build APKs for Android devices
  2. Expo: App credentials

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.

APKLint

Android inspection tools and practical release guides. About APKLint · Report a correction