Deliver to TestFlight and the App Store
Upload every signed iOS build to a TestFlight group, then send a tested build to the App Store.
On this page you turn on uploads to App Store Connect, so every build of the
iOS pipeline reaches your testers through TestFlight. Then you send a build
to the App Store.
The runner uploads from your Mac over outbound HTTPS, so this works in Local Only. Nothing needs to reach your Mac from the internet.
What you need
- The signed
iOSpipeline from Sign the iOS build for TestFlight. - Testers who are users of your App Store Connect team, for an internal TestFlight group.
- The TestFlight app on each tester’s iPhone.
1. Create a TestFlight group
- In App Store Connect, open your app and its TestFlight tab.
- Under Internal Testing, create a group, such as
Internal QA. - Add your testers to the group.
2. Turn on uploads
- In Oore, open the
iOSpipeline and its Publishing tab. - Under App Store Connect, check the readiness list. App Store distribution and App Store Connect API key both show as ready.
- Turn on Upload to App Store Connect after each successful build.
- For Destination, choose TestFlight.
- In TestFlight groups, enter
Internal QA. - Under Export compliance, leave Uses non-exempt encryption off if the app uses only encryption built into iOS, such as HTTPS.
- Select Turn on App Store publishing.
Testers see the app version’s release notes in What to Test. Oore drafts them from your commits; to write your own, use Edit on the build page’s Release notes card. See Release notes and changes.
3. Run a build
Select Run build, keep the iOS pipeline and branch, and select
Run build again.
After the build, sign, and artifact steps, the runner adds an
Upload to App Store Connect step (publish-app-store). It uploads the IPA to App Store Connect. Oore then
waits while Apple processes the build, answers the export compliance question,
and adds the build to Internal QA.
Check the result
- The build ends as Succeeded, with a succeeded Upload to App Store Connect step.
- On the build page, the Release tab first shows Processing. When Apple finishes, it shows Complete, because internal groups need no review.
- App Store Connect lists the build under TestFlight in
Internal QA. - Testers see the new build in the TestFlight app and can install it.
Apple’s processing usually takes several minutes, and sometimes longer.
4. Send a build to the App Store
When testers are happy with a build, send that same build to the App Store. First, fill in the app’s App Store listing in App Store Connect, such as screenshots, description, and privacy details. Apple rejects a submission without them.
Then choose one way:
- Promote the tested build. Add environments to the app and promote the TestFlight build into the App Store, with an approval if you want one. Nothing is rebuilt. See Promote builds between environments.
- Upload straight to the App Store. On the Publishing tab, change Destination to App Store and turn on Submit for review. Turn on Phased release to release over seven days. The next build is attached to the App Store version and submitted.
The release shows In review while Apple reviews it. Once the version is live, a phased release shows Rolling out until it is Complete.
Troubleshooting
The release fails with “has no app with bundle ID”
Create the app in App Store Connect with the same bundle ID, then run a new build.
The upload fails with a bundle version error
Apple already has a build with this build number. Bump the number after +
in pubspec.yaml’s version in a commit, then run a new build. If the
pipeline passes --build-number=$OORE_VERSION_CODE, raise
Build number offset instead; see
Version codes.
The App Store Connect upload fails after you fixed the cause
Select Retry App Store upload on the failed build. Oore uploads the stored IPA again without rebuilding or signing again. See Retry a store upload.
Testers need to install builds straight from Oore instead
That needs an Ad hoc distribution, registered devices, and an HTTPS address that the iPhone can reach, which Local Only does not provide. See Share builds with testers through Oore.
Next step
Your iOS app now reaches testers on every build. From here:
- Share builds with testers through Oore so your team installs ad hoc builds on registered iPhones, without TestFlight.
- Build on every push: turn on External Access, then connect GitHub or GitLab.
- Move the pipeline into
.oore.yamlso it is reviewed with your code. - Let your team sign in from their own devices.
For every App Store Connect setting, see Publish to TestFlight and the App Store.