React Native distribution
Get your React Native build onto a tester's phone.
Build a release APK or IPA, upload it, and send one link. Testers tap it on their phone and install. No Play Console track, no TestFlight review.
Step 1, Android
Build a release APK
From the project root. Gradle bundles your JavaScript into the app, so testers don't need Metro or your computer.
cd android
./gradlew assembleRelease
# the APK lands here
ls app/build/outputs/apk/release/app-release.apkOnly have an app-release.aab from bundleRelease? Run the AAB to APK converter on it, or build the APK as above. To see what you're about to send, drop the APK into the APK inspector.
Step 1, iOS
Export an IPA for registered devices
iOS only installs a build outside the App Store on iPhones listed in its provisioning profile, so collect your testers' UDIDs first. Send them to Get my UDID, add the devices in your Apple Developer account, then export.
In Xcode: open ios/MyApp.xcworkspace, pick Any iOS Device, then Product, Archive. In the Organizer choose Distribute App, then Release Testing. From the terminal, save this as ios/ExportOptions.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>release-testing</string>
<key>teamID</key>
<string>YOUR_TEAM_ID</string>
</dict>
</plist>cd ios
pod install
xcodebuild -workspace MyApp.xcworkspace -scheme MyApp \
-configuration Release -archivePath build/MyApp.xcarchive archive
xcodebuild -exportArchive -archivePath build/MyApp.xcarchive \
-exportOptionsPlist ExportOptions.plist -exportPath build/ipaXcode 15.2 and older call the method ad-hoc. The IPA lands in ios/build/ipa/. The IPA inspector tells you which devices it will install on before you send it. More on the Apple side in Apple's guide to registered devices.
Step 2
Upload it and send the link
Drop the file on this page, or upload it from wherever you build. Every upload of the same app goes under one link, so testers always land on the newest build.
npx appdropper upload android/app/build/outputs/apk/release/app-release.apkThe first run opens your browser to sign in. After that it prints the install link and a QR code in the terminal. Add --notes "Fixed checkout" to tell testers what changed.
name: Beta
on:
push:
branches: [main]
jobs:
android:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
cache: npm
- uses: actions/setup-java@v4
with:
distribution: temurin
java-version: 17
- run: npm ci
- run: ./gradlew assembleRelease
working-directory: android
- id: appdropper
uses: appdropper-io/upload-action@v1
with:
file: android/app/build/outputs/apk/release/app-release.apk
token: ${{ secrets.APPDROPPER_TOKEN }}
- run: echo "Install at ${{ steps.appdropper.outputs.install-url }}"Make a token under Settings, API tokens, and save it as the APPDROPPER_TOKEN repository secret. On pull requests the action also comments the install link.
lane :beta do
gradle(task: "assembleRelease")
app_dropper(file: lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH])
endInstall the plugin with fastlane add_plugin app_dropper and set APPDROPPER_TOKEN in the environment.
Working in Cursor or Claude Code? The App Dropper MCP server lets the agent upload the build and paste you the link.
Using Expo?
The upload is the same, the build isn't. EAS profiles, local builds and prebuild are covered in Expo app distribution.
React Native distribution questions
Do I need a keystore before testers can install it?
No. The React Native template signs release builds with the debug keystore until you set up your own, so assembleRelease gives an APK that installs anywhere. Make your own keystore before you publish to Play: once testers have a build, switching keys means they have to uninstall it before the next one installs.
Should I send an APK or an AAB?
An APK. Phones only install APKs; an .aab is what you upload to Google Play. If an .aab is all you have, the AAB to APK converter turns it into one APK you can share.
Why can't my iPhone testers install it?
Outside the App Store and TestFlight, iOS only installs a build on devices registered in its provisioning profile. Collect each tester's UDID, add it in your Apple Developer account, then archive and export again. App Dropper's device page collects UDIDs for you: testers open a link on their iPhone and tap once.
Is a debug build fine for testers?
Not usually. A debug build expects Metro running on your computer and shows a red screen without it. Send a release build: the JavaScript is bundled into the app and it runs on its own.
Can testers get the next build automatically?
Testers who join your app get an email or a push notification each time you upload a build, and the same link always serves the newest one. Builds are kept for 7 days on Free, 30 on Pro, 90 on Studio.
Does it work with Expo?
Yes, once you have an APK or IPA. How you get one depends on whether you use EAS Build, build locally or have prebuilt the native folders, so that has its own guide.
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