Release builds
A release build has your JavaScript bundled inside it, compiled to bytecode, so it runs without Metro. It's what you give to testers and publish to the stores.
- Android
- iOS
Before you publish
- Identifiers.
initnames the appdev.example.<name>, a placeholder. Set your ownandroid.packageandios.bundleIdentifierinapp.json. They can't change once the app is in a store. - Name, icon and version.
name,icon,versionand the splash screen are inapp.jsontoo. See Expo's app config reference. - Prebuild after changing any of them (When to run expo prebuild).
Android
Build and install a release build on the connected device in one step:
pnpm android --variant releaseTo build an APK file to share, build the generated project with Gradle:
pnpm exec expo prebuild --platform android
cd android
./gradlew :app:assembleReleaseThe APK is android/app/build/outputs/apk/release/app-release.apk. Install it with adb install -r app-release.apk. For Google Play, build an app bundle with ./gradlew :app:bundleRelease and sign it with your upload key; Android's guide to signing your app explains the keys.
iOS
On a Mac:
pnpm ios --configuration ReleaseTo publish, open ios/<YourApp>.xcworkspace in Xcode, choose your team under Signing & Capabilities, and use Product › Archive.
Over-the-air updates
A release build can download new JavaScript without a new store release, from Expo's update service (eas update). Expo Svelte has its own updates client for this: see Updates.