skip to content

In TestFlight, how do internal and external testers differ, and how does a new build reach each kind of tester?

level: juniorimportance: must knowfreq 70%

answer

  1. who already has an App Store Connect role
  2. 100 versus 10,000
  3. automatic distribution on internal groups
  4. review before the first external build
  5. builds marked TestFlight Internal Only

basics

~20 s

Internal testers are App Store Connect users with access to the app, up to 100, and get builds without review; external testers, up to 10,000 per app, join by email or public link, and their builds may need TestFlight App Review.

solid answer

~50 s

TestFlight splits testers by whether they are on your App Store Connect team. **Internal testers** are App Store Connect users with access to your content, up to 100; a build reaches them as soon as it is added to their group, or automatically when the group has *Enable automatic distribution* on. **External testers** are anyone else, up to 10,000 per app, invited by email or a public link into an external group; you can only create one after an internal group exists. Adding the first build to an external group sends it to **TestFlight App Review**, and testers get it once it is approved and they are notified. On both sides testers install the free TestFlight app, accept the invitation and can test a build for up to 90 days. A build uploaded as *TestFlight Internal Only* never leaves internal groups.

go deeper

for a junior

Recall who is internal (App Store Connect users with access) and who is external (everyone else), the 100 and 10,000 limits, and that testers use the TestFlight app.

for a middle

Explain the path of a build to each side: automatic distribution or manual adds for internal groups, and review plus notification for the first external build.

for a senior

Show you know the traps: Xcode Cloud builds need manual adds, internal-only builds cannot go external, and the external cap is shared by every group and link of one app.

for a principal

Speak to how a team uses the two tiers: internal groups for every build and fast feedback, external groups for a reviewed build that real users can try at scale.

## Two kinds of tester **TestFlight** is Apple's beta service inside **App Store Connect**: you upload a build, put it in front of testers, and collect their feedback before the release goes to the App Store. Every tester belongs to one of two kinds, and the kind decides how a build reaches them. | | Internal testers | External testers | |---|---|---| | Who they are | App Store Connect users with access to your content | People who are not App Store Connect users | | How many | up to 100 | up to 10,000 per app | | How they are invited | added from your team's users into an internal group | by email address, CSV import or a public link into an external group | | Review before testing | none | the first build added to a group goes to TestFlight App Review | | Who can manage them | Account Holder, Admin, App Manager, Developer or Marketing | Account Holder, Admin or App Manager | If someone you want as an internal tester is not offered in the dialog, the help pages tell you to change their user role: the internal list is drawn from your team, not from email addresses. ## How a build reaches internal testers 1. In the app's **TestFlight** tab, create a group with the add button next to *Internal Testing*. 2. Decide on **Enable automatic distribution**. With it on, Xcode delivers each new build to every member of the group; with it off, you add every build by hand. Builds created by **Xcode Cloud** must always be added to groups manually. 3. Invite testers from your team's users, then add a build and its **What to Test** notes. 4. Testers receive an email and accept it in the TestFlight app on their device, or with a redemption code on Apple TV. Internal testers can download and test all builds for 90 days, and every eligible build is also available to the *App Store Connect Users* group automatically. ## How a build reaches external testers 1. You must **create an internal group first**; only then can you add a group under *External Testing*. 2. Add a build to the external group and enter What to Test notes. Optionally tick **Automatically notify testers**; if you leave it off, you notify them by hand once the build is approved. 3. Depending on the build's status you click **Submit Review** or **Start Testing**: a build that still has to be reviewed is submitted, one that external testers can already have is started. The first build sent to external testers goes to **TestFlight App Review**, which checks it against the App Review Guidelines; later builds of the same version may not need a full review. 4. Invite testers by email or by sharing a **public link**, optionally limited by device and OS criteria and by a tester count. ## What the tester does - Installs the free **TestFlight** app, then accepts through the invitation email or the public link. - Installs a thinned variant of your app, gets updates as you add builds, and sends feedback from the TestFlight app or by taking a screenshot inside your beta. - Cannot use a Managed Apple Account created in a reserved domain: those accounts cannot test builds. - If the app includes an **App Clip**, can test both the app and the App Clip, with either one installed on a device at a time and a switch between them whenever they like. ## Rules that catch people - A build uploaded as **TestFlight Internal Only** from Xcode or Xcode Cloud is marked internal under its build number. It can go only to internal groups, never to external testers or to customers. - The external count is per app, so every external group and every public link draws on the same 10,000. - A build is testable for up to **90 days**, after which it is unavailable to testers. - TestFlight builds run their In-App Purchases in the **sandbox** environment, so a beta's purchase flow behaves like a sandbox purchase, not a live one. - Removing a build from a group is gentle: testers already using it keep access until they switch builds or stop testing. Cutting everyone off takes **Expire Build**. - External testers who joined by email show by name and email in App Store Connect; those who joined by public link show as anonymous. Uploading the archive, signing it, and automating that upload from a lane are separate lessons. What this question tests is the split itself: internal testers are your team and see builds straight away, external testers are everyone else and wait for Apple's beta review on the first build.

  • Can a build uploaded as TestFlight Internal Only be given to external testers later?
    No. Xcode and Xcode Cloud mark such a build as internal under its build number, and App Store Connect lets you add it only to internal tester groups; you cannot submit it for external testing or to customers. To reach external testers, upload a new build without the internal-only option and add that one to the external group.
  • How do In-App Purchases behave in a TestFlight build?
    Apps downloaded from TestFlight operate in the sandbox environment automatically. Subscriptions renew at an accelerated rate: daily, up to six times in one week, whatever their duration. To test other scenarios, such as billing retry, a tester signs into a Sandbox Apple Account under Developer settings, which works only for apps in your own developer account.
  • Why might Xcode Cloud builds never reach an internal group that has automatic distribution turned on?
    The help pages state that builds created by Xcode Cloud must always be added to groups manually in App Store Connect. Automatic distribution covers builds Xcode delivers, so a team using Xcode Cloud adds each build to the group itself or the testers see nothing new.

  • External testers need an App Store Connect account to install a beta.
  • Every internal build has to pass TestFlight App Review first.
  • Internal testers can be anyone with an email address, up to 10,000 people.
  • A TestFlight Internal Only build can be moved to an external group later.
  • You can create an external group before any internal group exists.