Set your app’s release identity
Set app names, versions, bundle identifiers, package names and the build destination without confusing a new app with an update.
Open Publish → Release settings. On mobile, choose Work first. These settings prepare the release package while the source remains available in Studio.
On this page
Understand the fields
| Field | What to enter |
|---|---|
App display name | The name shown on the device. |
Expo slug | The app’s Expo project-friendly name. |
App version | The user-facing release version, such as 1.0.0. |
Expo project ID | The verified project linked in Connections; this is not the store app ID. |
iOS bundle identifier | The Apple app identity, such as com.example.wandr. Keep the existing value for updates. |
iOS build number | The build’s identifier within the release; use a new appropriate build number for another upload. |
Android package name | The Android app identity, such as com.example.wandr. Keep the existing value for updates. |
Android version code | A positive integer that increases for new Android releases. |
Choose the build destination
Choose device testing or a store
Set Build destination to Device or simulator testing for a direct test, or Store testing or review for a store-compatible build.
Set the platform details
Use the iOS and Android tabs. For direct iOS testing, Test iOS on offers Registered iPhone or iPad and Simulator on a Mac.
Save the settings
Choose Save release settings and wait for Release settings saved. Ask the publishing agent to check the setup before preparing a build.
Why signing matters
Signing connects a build to the developer identity allowed to distribute it. On iOS, the certificate and provisioning profile must match the app, team and destination. Device testing also depends on the selected phones.
With Play App Signing, the upload key signs the bundle you send to Google. Google’s app signing key signs the app delivered to users. Keep access to the existing setup when updating an app; a newly generated unrelated key can prevent an update.
Check the exact build before approving
Changing source, account bindings or release settings can invalidate a prepared review. Request a fresh one. Download package exports preparation files; it does not by itself build, sign, upload or release the app.
Correct saved app and version.
Correct platform and build destination.
Correct Expo account and project.
Correct bundle identifier or package name and signing setup.
The action and any provider costs described by the review.
Example build review before a build starts. App and project values are illustrative.
- Confirm the app identity, version and Expo project.
- Check the output, build profile and environment.
- Review signing and package details before approving the build.