TestFlight beta testing for iPhone apps: what Apple's documentation says about internal and external testers
Plan TestFlight groups, beta review, feedback and build expiry using Apple's published internal and external testing guidance.
TestFlight is Apple's tool for sending test builds of an app to testers before it goes to the App Store. If an agency or developer builds your iPhone app, TestFlight is usually how you will first hold it in your hand. This article summarises Apple's own help pages as read on 15 November 2026. Limits and rules change, so check the pages before you plan around any number.
The steps Apple describes
- Provide test information: a beta description, what to test, and an email for feedback.
- Upload a build to App Store Connect. Apple says you may need to provide app encryption documentation after reading its export compliance page, that builds must include application identifiers within their provisioning profiles, and that a build can be tested for up to 90 days.
- Invite testers in groups. Apple's overview gives up to 100 internal testers (App Store Connect users with access to your content) and up to 10,000 external testers.
- Testers install the free TestFlight app and accept an invitation by email or public link.
- Watch build status and metrics, such as sessions and crashes, and resend invitations.
- Collect feedback. On TestFlight 2.3 or later for iOS, macOS and visionOS, testers can send feedback in the TestFlight app or by taking a screenshot inside your beta app; tvOS and older iOS versions send feedback to the email in step 1.
- Stop testing by expiring a build. Apple says that if you do not expire a build and then submit it to the App Store, invited testers can still test it after it goes live, and that builds become unavailable after 90 days.
Internal and external testers
Internal testers must be users on your App Store Connect account. External testers are anyone else, invited by email address, CSV import or a public link. Apple's rules on the external page:
- You must create an internal group before you can create an external group.
- Builds uploaded as "TestFlight Internal Only" from Xcode or Xcode Cloud can go only to internal groups.
- Inviting external testers may require a review. Apple says the first build you add to an external group is sent to App Review to check it follows the App Review Guidelines, only the first build needs a full review and later builds may not. You can submit up to six builds for TestFlight App Review in 24 hours, and only one build of each version can be in review at a time. If rejected, the rejection details appear in App Review in the sidebar.
- Required role for inviting: Account Holder, Admin or App Manager.
Public links
A public link can be open to anyone or filtered by criteria such as device and OS version, with an optional tester limit between 1 and 10,000. Apple warns that anyone can share the link, so testers could join without a direct invite. People who join by public link show as anonymous in App Store Connect, with install date, sessions and crashes still visible. You can change or deactivate the link at any time. People invited by email appear with name and address.
Omnistu advice for a project
- Treat TestFlight access as part of the contract. Who owns the Apple developer account the app is published under? Testers invited through an agency account may lose access if the account changes, and we have not researched account transfers.
- Add the first external build to your timeline early, since Apple says the first one needs a review.
- Be careful what a public link is used for. Because it can be shared, do not put confidential material or client data in a beta build that uses an open link; prefer email invitations for sensitive apps.
- Write "What to test" so a non-technical tester knows what to try, and give them a feedback route.
- Use fake data in beta builds. Do not point test builds at live customer data.
Limits
Two Apple help pages, the second only partly read (cut off after the email-invitation steps). The rest of that page and Apple's other TestFlight pages (such as the Apple-hosted background assets, export compliance and API) were not read. Numbers (testers, days, builds) are as Apple states them on that date. No claim about review times; Apple's pages we read give none for TestFlight. App Review Guidelines and privacy rules apply to beta builds too, and legal questions need counsel.
By Omnistu.