Current rules for inviting external TestFlight testers

What are the current rules for inviting external TestFlight testers

External testers are people you invite who are not App Store Connect users. To invite them, you first upload a build, create an external group, and wait for the build to pass TestFlight App Review. Apple says the first build you submit needs a full review before external testing starts.

The practical rule people miss is that internal testing and external testing are separate. Apple says you must create an internal group before you can create an external group, and builds marked as internal only from Xcode or Xcode Cloud stay internal only. If the build is tagged for internal use, you cannot send it to external testers.

You can invite external testers in two ways, by email or by public link. Apple says you can use one method or both. Email invitations go to specific addresses. A public link lets people join without a direct invite, which is useful when you want a wider pool and do not want to manage every tester individually.

Public links can be open to anyone, or filtered by criteria. Apple says you can set device or platform requirements so only eligible testers can accept the link. You can also set a tester limit for the link, from 1 to 10,000 people, and you can deactivate the link whenever you want. That limit applies to the public link in that group.

Apple also allows up to 10,000 external testers per app. That is the outer cap for external testing, not a promise that every tester should be added at once. For many teams, the cleanest setup is a small external group with a focused build, a clear testing note, and a link or email list that matches the people who can actually test the device you built for.

Before an external build is shared, Apple asks for test information for App Review. The TestFlight pages say you need beta app description and beta app review information for external testers, plus test information such as what you want people to test and contact details. If that information is missing, the build can sit in review instead of reaching testers.

Managed Apple Accounts created in reserved domains cannot be used to test builds. That matters when a team tries to reuse company-managed accounts as external testers. Apple also says App Store Connect users with the Admin role get the approval email when Apple approves the build for TestFlight testing, so the account owner should watch the review status rather than guessing from the tester side.

The inconvenient part is review timing. You can only have one build of each version in review at a time, Apple says, and you can submit up to six builds for TestFlight App Review in 24 hours. If you upload replacements too fast, you do not speed things up, you create a queue. For a live beta, that means planning the next build before you need it.

A good workflow is simple. Upload the build, add the build to an external group, fill in the testing notes, choose email or public link, and then distribute after approval. If you use a public link, decide whether the test is open or filtered, then set the link limit to match the number of people you want in that group. If you use email, import the addresses you actually want to test.

The part people get wrong is assuming TestFlight is just a sharing tool. Apple treats external testing as a reviewable beta distribution path, not a casual file drop. If you want a wider prelaunch loop, use TestFlight for the beta and keep your test instructions specific. If you want a different workflow for matching testers, DevConnect is built for exchanging real testing on owned apps, not for posting or automating on other platforms. https://devconnectplatform.com

If you need the shortest version, it is this: external TestFlight testers must be invited from an external group after the build is approved, and you can invite them by email or public link. Public links can be open or filtered, can be limited, and can be turned off. The build, the group, and the review step all have to line up before testers can join.

FAQ

Can I invite external testers before Apple approves the build No. Apple requires the build to pass TestFlight App Review before external testers can use it. You can prepare the group and the invitation setup first, but the build itself must be approved before external distribution starts.

Can I use a public TestFlight link instead of collecting emails Yes. Apple says external testers can join by public link, and that link can be open to anyone or filtered by device and platform criteria. You can also set a tester limit for that link and deactivate it later.

Do internal testers count the same way as external testers No. Apple keeps them separate. Internal testing uses App Store Connect users with access to your content, while external testing is for people outside App Store Connect. Builds marked internal only cannot be sent to external tester groups.

What stops a tester from joining an external link A tester can be blocked by the link criteria, by the tester limit, by an inactive link, or by using an account type Apple says cannot test, such as certain Managed Apple Accounts in reserved domains. The build also has to be approved and active for external testing.

How many external testers can one app have Apple says up to 10,000 external testers per app. That is the published cap for external testing on TestFlight.