Release setup
Prepare the native configuration and store handoff before you create production binaries.
Open Release
In the studio, open Release. The release passport tracks build identity, artwork, listing copy, public links, and the store review contact. You can save a partial packet and return later.
Values embedded in the app
| Setting | Where it goes |
|---|---|
| Display name + public version | Expo app config; shown on the installed app and store build |
| iOS build number + Android version code | Local/source-build seeds; EAS production counters increment remotely |
| Deep-link scheme | Native iOS and Android URL handling |
| iPad + encryption choices | Native iOS build configuration |
| Bundle ID, icon, and splash | Native identity and packaged artwork |
Store handoff packet
Listing descriptions, category, keywords, release notes, support/privacy links, and reviewer contact details are saved with the app. Source downloads include release/store-metadata.json and release/STORE-CHECKLIST.md so the listing stays matched to the binary.
What still happens in the stores
Appify prepares the binary and handoff, but you still complete screenshots, pricing, territories, age/content ratings, Google Play data safety, Apple privacy answers, and any reviewer login credentials in App Store Connect or Play Console.