Did Apple change TestFlight external tester requirements?

Did Apple change what TestFlight external testers need before I can invite them

Yes. Apple still lets you invite external testers by email or public link, but the first build you share outside your team must go through TestFlight App Review before testers can install it. External testers then accept the invite in the TestFlight app.

The part people get wrong is mixing up the invite with the review. You can create the external group and send the invitation, but Apple does not let that first external build reach testers until App Review approves it. Apple says the first build of an app sent to external testers is submitted to TestFlight App Review, and the review is only required for the first build of a version.

The inconvenient part is that the approval gate is on the build, not on the person. An external tester is just someone outside App Store Connect who receives an email invite or public link. If the build is not approved yet, the invite exists, but the tester still cannot start testing that build.

Apple’s current setup is simple on the tester side. External testers accept the invitation in the TestFlight app, and Apple can enforce device and OS criteria when you use a public link. The tester does not need UDIDs or provisioning profiles, which is one reason TestFlight stays easier to manage than older beta distribution methods.

What changed in practice is not the invitation flow, it is the requirement before a new external tester can actually see the build. Apple now makes the first external build pass TestFlight App Review, and that review is only needed for the first build of a version. Later builds for the same version may skip full review, which is why teams sometimes see a fast second upload after a slow first one.

If you are coming from internal testing, do not assume the same rules apply. Apple separates internal testers from external testers, and internal testing is the lower-friction path for team members inside App Store Connect. External testing is the path that triggers the extra review step, so a clean internal test does not guarantee immediate external access.

Apple also caps external access at 10,000 testers per app, which is enough for most beta programs but still a hard ceiling. Internal testers are capped separately, and Apple documents different limits for the two groups. That difference matters because some teams mistakenly try to use an internal setup as a shortcut for external distribution, then discover the review gate still applies.

If your goal is simply to get real users into the beta, the correct sequence is: upload the build, create or select an external group, submit the first build for TestFlight App Review, wait for approval, then send email invites or a public link. If you skip the review step in your planning, the tester list can be ready while the build is still blocked.

For teams that also test Android, this is one place where Apple and Google do not match. Google Play’s closed testing flow has its own tester-count and timing rules, while TestFlight uses App Review plus invite acceptance instead. If you are organizing testers across both platforms, keep the Apple path separate so you do not carry Android assumptions into iOS. If you need a simple way to coordinate testers you already know, DevConnect keeps that exchange on your own terms and stays free to use: https://devconnectplatform.com.

A common failure mode is to treat the public link as instant access. Apple lets you use a link, but the build still has to clear review first. Another common failure is to assume every new build needs the same delay. Apple says the first build of a version is the one that requires TestFlight App Review, so later builds for that same version are usually faster to reach testers.

If you are trying to debug a stalled beta, check three things in order: whether the build has been added to an external group, whether the first build has finished TestFlight App Review, and whether the tester accepted the invitation in the TestFlight app. Those are separate steps, and one missing step can make the whole process look broken even when Apple is behaving as documented.

FAQ

Do external testers need to be App Store Connect users? No. Apple defines external testers as people you invite who are not App Store Connect users, and they join through email invite or public link.

Can I invite external testers before the build is approved? Yes, you can set up the external group and send the flow, but the first external build still must clear TestFlight App Review before testers can install it.

Do later builds need the same review again? Apple says review is required for the first build of a version, and later builds for that same version may not require full review.

How many external testers can I invite? Apple documents up to 10,000 external testers per app.

What do testers actually install? Testers use the TestFlight app on the device they plan to test on, then accept the invite and access the builds you made available to them.