Expo distribution
Share your Expo app with testers, with or without EAS.
Get an APK or IPA out of your Expo project, upload it, and send testers one link that always has your newest build.
Step 1
Make a build phones can install
EAS builds an .aab for Android by default, which phones can't install. Give a profile "buildType": "apk" in eas.json:
{
"build": {
"preview": {
"distribution": "internal",
"android": { "buildType": "apk" }
}
}
}Then build it whichever way suits you. All three give the same kind of APK.
eas build -p android --profile previewRuns in Expo's cloud and gives you a download link for the APK when it finishes. Counts toward your plan's monthly builds.
eas build -p android --profile preview --local --output app-preview.apkThe same build, run on your computer instead of Expo's servers. It needs Java 17 and the Android SDK installed, and it doesn't wait in a queue.
npx expo prebuild -p android
cd android
./gradlew assembleRelease
# android/app/build/outputs/apk/release/app-release.apkGenerates the native android/ folder and builds it like any React Native app. The release build is signed with a debug key until you add your own, which is fine for testers.
Out of EAS builds this month?
Expo's free plan comes with a monthly build allowance and a slower queue. When you hit the limit, or a build sits waiting, add --local to the same command. It runs the identical build on your own computer at no cost, and App Dropper gives you the install link EAS would have.
For iOS, local builds need a Mac with Xcode. Android local builds work on macOS and Linux, and on Windows through WSL.
Step 2
Upload it and share the link
Drop the APK at the bottom of this page, or upload straight from the terminal:
npx appdropper upload app-preview.apk --notes "New onboarding"You get a link and a QR code. Testers open it on their phone and tap install. Uploading the next build of the same app updates that link and lets testers know. Building with an AI agent? The MCP server lets Cursor or Claude Code upload it for you.
Not using Expo's tooling for builds at all? See React Native app distribution for Gradle and Xcode, including iOS export settings.
Expo distribution questions
Why did EAS give me an .aab?
Android builds default to an App Bundle, because that's what Google Play wants. Phones can't install it. Add "buildType": "apk" to the profile, as above, or run the bundle you already have through the AAB to APK converter.
Isn't Expo Go enough?
For you, while developing, often yes. For testers it falls short: they have to install Expo Go, your app can only use the native modules Expo Go ships, and it isn't your app icon on their home screen. A preview build is the real app.
EAS already gives me an install page. Why use App Dropper?
If EAS Build and its internal distribution page cover you, keep using them. App Dropper helps when the build doesn't come from EAS's cloud, such as a local or Gradle build, and when you want one link per app that always has the newest build, with testers notified each time you upload.
What about iPhone testers?
Run eas build -p ios --profile preview. Internal distribution builds an ad hoc IPA, which only installs on devices registered in your Apple Developer account. Testers can find their UDID with App Dropper's Get my UDID page, or you can use eas device:create. Rebuild after adding devices, then upload the IPA.
Do testers need a new build for every change?
Not if you use EAS Update. JavaScript changes reach installed preview builds over the air. You only need a new build when native code or config changes, such as a new native module or permission.
Upload your build
Drop the .apk or .ipa. You get an install link and a QR code.
Drag & drop your build
or browse files — .apk or .ipa, up to 150 MB