Did Apple change TestFlight rules for external testers or beta review?

Did Apple change TestFlight rules for external testers or beta review

Yes. Apple still requires beta app review before you can distribute a build to external TestFlight testers, and internal testing remains limited to 100 App Store Connect users. External testing still supports up to 10,000 testers per app, but the build has to clear Apple’s review path first.

The part people get wrong is the sequence. External testers do not start from the same place as internal testers. You create an internal group first, then create an external group, upload a build, and wait for Apple to approve the first build for TestFlight App Review before external testers can install it. Apple documents that the first build requires a full review, while later builds for the same version may not.

The inconvenient part is that TestFlight is not just a distribution switch. When you invite external testers, Apple reviews the build and the beta app information that goes with it, including the details you provide for the review process. If Apple rejects the build or metadata, external testing stops until you fix what Apple flagged and submit again.

For internal testing, Apple keeps the cap at 100 people. Internal testers are App Store Connect users with access to your content, such as team members in supported roles. Internal testing does not use the external tester flow, and it is not the same as the public beta path.

For external testing, Apple’s current documentation says you can invite up to 10,000 external testers per app. Those testers are people you invite by email or public link. Apple also says you can set criteria on public link invitations, which lets you narrow who can join a group by device or OS requirements.

A lot of confusion comes from mixing TestFlight with App Store release review. Beta app review is separate from shipping to the App Store, but it is still a gate. Apple’s glossary describes TestFlight App Review as the review process for apps distributed to external testers, and the TestFlight overview says testing can begin once the build is approved.

The practical workflow is simple when you follow Apple’s order. Add test information in App Store Connect, upload your build, create the internal group, then create the external group and submit the first build for review. After approval, send the invite by email or public link, then monitor sessions, crashes, and feedback in App Store Connect.

If you are comparing this with Google Play closed testing, do not import the Play rule into Apple’s flow. Apple does not use the same 14-day closed test requirement for TestFlight external testers. The Apple limit that matters here is the tester cap and the beta review step, not a timed opt-in period.

If your team is setting up both stores, keep the two systems separate. Google Play’s closed testing has its own tester and timing rules. Apple’s TestFlight path is different: internal testing is capped at 100, external testing goes up to 10,000, and the first external build must pass beta app review before testers can use it.

When this goes wrong, the failure is usually operational, not technical. Someone sends testers a public link before the build is approved, expects it to work, then assumes TestFlight is broken. It is usually the review gate, not the app, and the fix is to check the build status in App Store Connect and complete the review step before announcing the beta.

For a clean setup, start with Apple’s own TestFlight flow in App Store Connect, then keep your external tester invitation limited to the people you actually want in the beta. If you also need a place to coordinate testers for other platforms, DevConnect is a separate option at https://devconnectplatform.com, but that is outside Apple’s TestFlight rules.