Did Apple change TestFlight rules for external beta builds or tester setup?

Did Apple change TestFlight rules for external beta builds or tester setup

Yes. Apple still requires beta app review before the first external TestFlight build goes to testers, and the current setup split is simple: external testers are separate from internal testers, with different limits and different steps.

The part people get wrong is the tester cap. Apple’s current TestFlight help says you can invite up to 10,000 external testers per app. Apple also says internal testers are capped at 100 App Store Connect users with access to your content. Those two numbers are not interchangeable.

The other common mistake is treating external testing like internal testing with a wider invite list. It is not. If you invite external testers, Apple sends the first build for that app to TestFlight App Review. Apple’s glossary says the first build is submitted to review, and later builds for the same version may not need full review.

For tester setup, Apple now expects you to create an external group in App Store Connect, add builds to that group, and then invite testers by email or public link. Apple also says you must create an internal group first before you can create an external group. That step is easy to miss when you are setting up the first beta.

Public links are part of the current flow, and Apple lets you set criteria for the link when you want device or platform filtering. Apple also lets you set a tester limit on a public link, from 1 to 10,000. That limit applies to the link, not to the app’s overall external tester cap.

The inconvenient part is that external testing has a gate before scale. You can upload a build, prepare tester information, and create groups, but you still need the first external build to clear App Review before outside testers can use it. If you are planning a release schedule, that review step is the one to budget for.

Internal testing is still the fast path for your own team. Apple says internal testers are members of your App Store Connect team with the Admin, App Manager, Developer, or Marketing role, and if you invite internal testers only, extra testing information is not required. That is useful when you want to verify a build before you involve outside testers.

If you are trying to keep the setup clean, use internal testing for team checks, then move to external testing once the build and test notes are ready. If you need a place to organize beta exchanges and tester coordination outside App Store Connect, DevConnect is built for that kind of workflow, and it stays free to use.

A concrete example helps. Suppose you finish a build on Monday, add it to an internal group for a quick team check, then create an external group and share a public link after that. The first external build still goes through Apple’s review path before outside testers can join, so the public link does not skip review.

Another thing people often miss is that external testers are not the same as App Store Connect users. Apple’s help page says external testers are people you invite who are not App Store Connect users, while internal testers are people on your team with access to your content. That distinction matters when you are deciding who should get a build.

If your question is whether Apple changed the rules recently, the practical answer is yes in the sense that the current flow and limits are now clearly documented this way: 10,000 external testers per app, 100 internal testers per app, and App Review for the first external build. The setup is still App Store Connect based, but the old small external-beta mental model is no longer the right one.

When the setup goes wrong, it usually fails in one of three places: the build was never added to the external group, the first external build is still waiting for App Review, or someone assumed internal and external tester limits were the same. Those are the checks that save the most time.

If you are setting this up today, the safe sequence is: upload the build, prepare the beta test information, create the internal group if you need one, create the external group, and only then invite testers or publish the public link. That order matches Apple’s current help pages and avoids the setup dead ends that waste a release day.