Did Apple change TestFlight rules for external testers

Did Apple change TestFlight rules for external testers

No. Apple still lets you invite up to 10,000 external TestFlight testers, and Apple’s documented flow still uses App Store Connect groups, TestFlight App Review for the first external build, and invitation by email or public link. The rule people are remembering is from Google Play, not Apple.

The current Apple guidance says external testers are people you invite who are not App Store Connect users. You create an external group, add builds, and invite testers. Apple also says the first build you add for external testing goes to TestFlight App Review, and later builds may not need the same full review.

Apple’s external tester ceiling is still 10,000 people per app. Apple also separates internal testers from external testers, with up to 100 internal testers tied to App Store Connect roles. That split matters because internal testing and external testing are not the same track, and they do not use the same invite flow.

The part people get wrong is mixing Apple TestFlight with Google Play closed testing. Google Play now requires a closed test with at least 12 opted-in testers for 14 continuous days before a newly created personal account can request production access. Apple has no equivalent 14-day external-tester requirement in TestFlight.

The inconvenient part is that Apple still keeps a review gate on external TestFlight builds. You do not get to skip App Review just because the build is for beta testing, and you do not get a guarantee that every build will sail through without friction. The first build for a group is the one that reliably triggers the review step.

If you are comparing platforms, the practical difference is simple. On Apple, you can recruit external testers by email or public link and start once the build is approved. On Google Play, an account in the newer personal-account category has to clear the closed-test requirement before production access becomes available. Those are separate systems with separate gates.

If your goal is to run a real beta, TestFlight still works the same way: upload a build, create a group, choose whether the group is internal or external, then send invites. Apple says testers can install the free TestFlight app, accept the invite, send feedback, and receive updates for up to 90 days per build.

If you are organizing testers across platforms, do not treat Apple and Google as interchangeable. A TestFlight invite does not satisfy Google Play’s closed-testing rule, and a Google Play closed test does not replace Apple’s TestFlight setup. If you are coordinating both, keep the tracking separate so one platform’s rules do not get mistaken for the other’s.

For teams that want a structured tester exchange instead of buying installs, DevConnect is built around testing on apps you own or control. The site’s public positioning is that it is free to use, with no paid tier, no trial ending, and no credit card. Use that kind of workflow for coordination, then still follow Apple’s and Google’s own testing rules for distribution. https://devconnectplatform.com

The bottom line is that Apple did not introduce a new 12-tester, 14-day external TestFlight rule. Apple’s current docs still show the long-standing external-tester model, public links or email invites, a first-build review, and up to 10,000 external testers per app. The change happened on Google Play, and that is the rule most people are really asking about.

What to check if your TestFlight rollout looks blocked

First, confirm whether you are actually in Apple’s external testing flow. If you are using TestFlight, you need an external group in App Store Connect, a build assigned to that group, and at least one approved build before external testers can join. If any of those pieces are missing, the issue is setup, not a new Apple policy.

Second, check whether the tester invite is internal-only. Apple says builds uploaded as TestFlight Internal Only can only be added to internal tester groups. That is a common mistake when a build is created for the team but later someone tries to use it for outside testers. The build type controls the path.

Third, check your public-link settings if you are using one. Apple lets you cap the number of people who can join through a public link, and you can also filter by criteria such as device or platform. If the link is disabled, capped, or too restrictive, people may think TestFlight is broken when the invite is simply no longer accepting them.

Why this confusion keeps happening

Apple and Google both use the word “testers,” but the gates are different. Apple focuses on App Store Connect roles, build review, and an external tester cap. Google Play focuses on testing tracks and, for certain personal accounts, a closed-testing threshold before production access. When someone says “the rules changed,” the first question is which platform they mean.

Practical example

If you are shipping an iOS beta to 40 customers, TestFlight can handle that through an external group and a public link or email invites, as long as the first build is approved. If you are also shipping the Android version from a newer personal Google Play developer account, that Android release still needs the separate 12-tester, 14-day closed-test path before production access. One project, two rule sets.

What changed, and what did not

What changed is Google Play’s closed-testing requirement for newly created personal accounts. What did not change is Apple TestFlight’s external-tester model. Apple still allows up to 10,000 external testers per app, still routes the first external build through App Review, and still lets you invite testers by email or public link.