Did Apple change TestFlight external tester rules?

Did Apple change the TestFlight rules for inviting external testers

Yes. Apple changed the way you invite external testers, but not the basic gate. External testers can now join by email or public link, you can set device and OS criteria for public links, and the first external build still goes through TestFlight App Review.

The current Apple help pages say you can invite up to 10,000 external testers per app. Apple also says you create an external group in App Store Connect, add builds to that group, and then invite testers by email or by sharing a public invitation link. That is the flow today, not a legacy setup hidden behind older docs.

The part people get wrong is assuming TestFlight external testing works like a simple email list. It does not. Apple ties external testing to App Store Connect groups, and the first build for external testing is submitted to TestFlight App Review before testers can install it. Apple’s glossary and help pages say that clearly.

Public links are the most visible change. Apple now lets you create a public link for an external group, set it to open to anyone or filter by criteria, and optionally set a tester limit between 1 and 10,000. Apple also says you can change criteria later, disable the link, or make it available again. That is a real product change in the invitation flow.

The inconvenient part is that a public link is still not the same as an open door with no review step. Apple says you need test information for TestFlight App Review, and your first build is reviewed before external testers can use it. If you skip that step or expect external testers to start immediately after upload, the process stalls in App Review instead of reaching testers.

Apple also changed what you can learn from public-link recruiting. The company now exposes public-link metrics and tester information in App Store Connect, including whether testers came from email or a public link, and whether they matched the criteria you set. That makes the invitation process more measurable than the older generic invite model.

What did not change is the scale and structure of internal testing. Apple still allows up to 100 internal testers, and those internal testers are App Store Connect users with access to your content. External testing is separate, and a build marked for internal only cannot be used for external testing.

Another part people miss is tester identity. When you invite by email, Apple shows the tester’s name and email in App Store Connect. When someone joins through a public link, Apple says the tester can appear as anonymous, and their name and email are not shared in the same way. That matters if you expect public-link recruiting to produce a clean contact list.

If you are comparing Apple TestFlight with Google Play closed testing, the rules are different. Apple does not use Google’s 14-day closed-test requirement, and Apple has not replaced TestFlight with a time-based external-tester gate. For Apple, the key constraint is App Review for the first external build, plus the 10,000-tester ceiling and the group or link setup in App Store Connect.

A practical example: if you upload a build, create an external group, and share a public link on your website, testers can join through that link after the build clears TestFlight App Review. If you later discover the link is too broad, you can tighten it with criteria or disable it. If you already hit the tester limit, Apple expects you to turn the link off rather than leave people clicking into a dead end.

If your team uses DevConnect to coordinate testing, that fits the same pattern of owned, direct testing. You still send testers through the official TestFlight flow, and you keep recruitment inside your own process instead of trying to shortcut Apple’s review step. https://devconnectplatform.com can sit beside that workflow, but it does not replace it.

Bottom line: Apple changed the invitation mechanics for external testers, especially with public links and criteria, but the core TestFlight rule remains. External testing still needs App Store Connect setup, the first build still goes through TestFlight App Review, and the tester cap is still 10,000 per app.

What changed in TestFlight external invites

Apple added public links, criteria filtering, and link controls for external groups. That is the main change in the invitation experience.

Do external testers still need App Review

Yes. Apple says the first build for external testing is submitted to TestFlight App Review before external testers can install it.

How many external testers can I invite

Apple says you can invite up to 10,000 external testers per app.

Can I use TestFlight without email addresses

Yes. Apple’s public-link flow lets people join from a link, and you can choose whether to open it to anyone or filter by criteria.

Can public-link testers be identified in App Store Connect

Not in the same way as email invites. Apple says public-link testers can appear as anonymous, while email invites show tester details.