Shipping my first iOS app with Expo: three kinds of build, 15 builds a month and TestFlight
Cover: Paper Airplane by Andrey Larin, CC0 1.0.
Background
The app was done and every feature worked on my own iPhone, so I thought the last step was "make a production build". The build finished and TestFlight showed nothing. Then I opened Expo's billing page and saw that the free plan limits how many builds I get each month.
I wanted to understand what each kind of build is for, how to save builds and how to get the real thing onto my own iPhone.
What I tried
- A new build for every change: I used several builds in a day, and most of those changes never needed one.
- Downloading the .ipa and installing it: it wouldn't install, because an App Store-signed .ipa has no registered devices.
- Waiting for the build in TestFlight: it never came, because I hadn't uploaded it.
- Taking App Store screenshots from the web version on Windows: flags turned into letters and the fonts weren't iOS fonts, so I dropped it.
How I did it
1. Know the three kinds of build
| Development | Preview | Production | |
|---|---|---|---|
| How to install | Link or QR code | Link or QR code | Only through TestFlight or the App Store |
| Where the JavaScript comes from | A dev server on your computer | Bundled in the app | Bundled in the app |
| Same as what users get | No, it runs in debug mode | Nearly | Exactly |
2. Use the development build for everyday changes
Once a development build is installed, JavaScript changes need no new build. Keep the dev server running on your computer and the phone shows each change straight away. Only native changes need a rebuild, such as Swift code, permission settings or a package with native code. I now save up a few native changes and build once.
3. Check the .ipa before uploading
My app uses Apple Intelligence, which only exists on iOS 26, so older iPhones have to skip it cleanly. An .ipa is just a zip. Unzip it, read the main binary's load commands, and you can see whether that framework is weakly linked:
LOAD .../VisionKit.framework/VisionKit
WEAK .../FoundationModels.framework/FoundationModels
WEAK means older iOS versions won't crash at launch.
4. Upload to TestFlight with eas submit
eas build --platform ios --profile production
eas submit --platform ios --latest
Uploading doesn't use a build. Apple takes ten minutes or more to process it. Then create an internal testing group under TestFlight in App Store Connect, add yourself and install it from the TestFlight app. Internal testing needs no review.
5. Three things before review
- App Privacy: everything stays on the phone, so the answer is "Data Not Collected".
- EU trader status: an individual account that declares itself a trader has to show an address, phone number and email on EU App Store pages. A free app with no ads can declare itself a non-trader. If I add ads later, I'll look at this again.
- Screenshots: take the raw shots on a real iPhone, then let a script add the caption and background and produce both languages in one go.
What tripped me up
- The first build asks you to sign in to Apple: I walked away and came back to find the build still waiting, never started.
- Don't say yes to Push Notifications without a reason: my app only uses local notifications, so saying yes just left me with a push key I don't use.
- My computer went to sleep: the dev server stopped, so the development build couldn't connect.
- A finished production build isn't in TestFlight yet: you still have to submit it.
What improved
- UI changes show up on the phone straight away and use no build.
- Native changes are saved up, so a few of them share one build.
- Testing the release goes through TestFlight instead of trying to install the .ipa.
- Before uploading I check weak linking, entitlements and the version number.
Use AI to apply it
If you are about to ship your first iOS app with Expo, paste this into your AI coding assistant:
I'm shipping an Expo app to the App Store on the free EAS plan (15 iOS builds a month).
1. Look at my app config, eas.json and native modules, and tell me which of my
planned changes need a new native build and which only need a JS reload.
2. Suggest a build plan for this release that uses as few builds as possible.
3. After the production build, download the .ipa, list the frameworks the main
binary links (weak or required) and the entitlements in its provisioning
profile, and flag anything that would crash on the minimum iOS version.
4. Walk me through eas submit and TestFlight internal testing, and list what
App Store Connect still needs before review (privacy answers, EU trader status,
screenshots).