TestFlight is Apple's beta distribution service: up to 100 internal testers from your App Store Connect team and up to 10,000 external testers by email or public link, with each build available for 90 days. For AI-built apps it is the most important safety net before App Review, because it exposes the device, network and permission issues that agents cannot see in a simulator.
On this page
An app written largely by a coding agent has a particular risk profile. The code paths the agent tested work well. The paths nobody thought of, such as a denied permission, a flaky network, an older phone or an interrupted purchase, are untested by definition. TestFlight is where those paths meet real people and real devices before an App Store reviewer finds them. Used deliberately, it shortens the time to approval rather than lengthening it.
How TestFlight works
Every build you upload to App Store Connect can be distributed through TestFlight once it finishes processing. Internal testers are members of your App Store Connect team with appropriate roles; you can add up to 100, and they can test builds without review. External testers are anyone else, invited by email or through a public link, up to 10,000 per app. The first build you send to external testers must pass Beta App Review, which is usually faster than a full App Review and checks basic guideline compliance. Later builds of the same version may not need a full review again. Each build is available for 90 days after upload, after which testers can no longer install it.
Testers install the TestFlight app, accept the invitation and receive updates automatically. They can send feedback with screenshots directly from the app, and crash reports reach you in App Store Connect and Xcode's Organizer.
A test plan written for agent-built code
Generic "please test the app" invitations produce generic feedback. Give testers a short, focused plan. For AI-built apps, these are the areas where we find the most issues:
- First run and onboarding: fresh install, every permission prompt answered with "Don't Allow" once, then with "Allow".
- Accounts: sign-up, email verification, password reset, sign-out, account deletion inside the app.
- Network conditions: airplane mode, slow connections, switching from Wi-Fi to mobile data in the middle of an action.
- Devices and settings: the smallest supported iPhone, an iPad if the app runs there, large text sizes, dark mode, VoiceOver on the main screen.
- Interruptions: a phone call or app switch during a form, a purchase or an upload.
- Purchases: subscription start, cancellation and restore, using sandbox accounts.
For apps that wrap a web app in a native shell, add native features to the plan explicitly: push notification opt-in and delivery, deep links, file uploads, biometric login and the offline screen. These are what make the app more than a website, and they are what reviewers check under Guideline 4.2. A wrapper such as WebViewGold provides these features out of the box, but each must still be configured and tested with your app.
Closing the loop with your agent
TestFlight feedback becomes useful when it turns into fixes quickly. A workflow that works well: collect feedback and crash reports daily, have a person triage them, and give each confirmed bug to the coding agent as a task with the steps to reproduce, the device, the iOS version and the screenshot. Ask the agent to write a failing test that reproduces the bug before it changes code. For crash reports, provide the symbolicated stack trace; agents are good at locating the cause in their own code when they see the exact frame.
Automate uploads so that testing never waits on a person. Fastlane's upload_to_testflight action or Xcode Cloud workflows can upload every main-branch build and notify a tester group. Our article on Fastlane plus Claude Code describes such a pipeline.
Practical pitfalls
A few things catch teams out. External testing requires test information in App Store Connect, including a feedback email and, if there is a login, a demo account for Beta App Review. Builds that use encryption need the export compliance answer, which you can set once in the Info.plist with ITSAppUsesNonExemptEncryption to avoid answering it on every upload. Builds pointing at a staging backend must not go to external testers who expect real data, so make the environment visible somewhere in the app's settings screen. And remember the 90-day expiry: long-running beta programs need a fresh build at least every three months.
How long to test
There is no rule from Apple. For a first release we recommend at least one full week with external testers covering both small and large devices, and longer if the app handles payments or sensitive data. Every crash found in TestFlight is one that a reviewer, and later a user with a one-star rating, does not find. The Android counterpart is the Google Play testing tracks, where new personal accounts currently must run a closed test with at least 12 testers for 14 days; see Google Play closed testing explained.
Support for the whole publishing process
Setting up groups, test information, Beta App Review and then the final submission is a process in itself. AppSubmitter.io provides hands-on help from TestFlight setup through App Review until the app is live, and supports Google Play in parallel. Once testing is complete, work through the App Store submission checklist for Claude Code and Codex projects before you submit.
Frequently asked questions
Do internal TestFlight builds need Apple review?
No. Internal testers from your App Store Connect team can install builds as soon as processing finishes. Builds for external testers go through Beta App Review.
How many testers can I invite?
Up to 100 internal testers and up to 10,000 external testers per app, at the time of writing.
Why can my testers no longer install the beta?
TestFlight builds expire 90 days after upload. Upload a new build and make it available to the tester groups.
Can a TestFlight public link be shared with anyone?
Yes, anyone with the link can join until the tester limit you set is reached. The build must first pass Beta App Review.