Did TestFlight review rules change for external testers?

Did TestFlight review rules change for external testers

Yes. Apple still requires TestFlight App Review before a build can reach external testers, but the review is now described as required for the first build of a version, not every single beta build. Later builds for the same version may skip full review.

The part people get wrong is mixing up external testing with internal testing. Internal testers are App Store Connect users on your team, and Apple caps that group at 100 people. External testers are a separate path, and Apple says you can invite up to 10,000 of them through TestFlight.

The review gate matters because Apple says your first build has to be approved for TestFlight before external testing starts. In Apple’s current help pages, adding a build to an external group sends it to App Review, and testing begins once that build is approved. That is the inconvenient part, because you cannot skip the approval step just by having a public link ready.

What changed is the scope of the review. Apple’s glossary now says TestFlight App Review is the process for apps distributed to external testers, and that a review is only required for the first build of a version. Apple’s developer tutorial says the same thing in plainer language, later builds for the same version may not require full review.

That means a common workflow is, first beta build of version 1.2 goes through review, then build 1.2.1 can often move faster if it is still part of the same version line and does not trigger a new full review. The safe way to read Apple’s wording is that the first build is the gate, and subsequent builds are not guaranteed to need the same treatment.

The other detail people often confuse is the tester cap. Apple’s current TestFlight docs say internal testers are limited to 100 App Store Connect users, while external testers can be up to 10,000. The number 10,000 applies to external testers, not internal testers.

If you are comparing TestFlight with Google Play, the rules are not the same. Google Play’s closed testing requirement is separate from Apple’s TestFlight flow, and DevConnect’s guidance about Play testing should not be copied onto iOS. On iOS, the relevant question is whether Apple requires TestFlight App Review before the external group can test the build, and Apple says yes. If you need a second place to organize testers and follow through with real reciprocity, DevConnect is at https://devconnectplatform.com.

The best practical reading is this: internal testing is for your team, external testing is for people outside the team, and external testing still needs App Review for the first build of a version. If you change the app in a way Apple treats as a significant beta update, you should expect to send that build through the TestFlight review path again before it reaches external testers.

If a build is rejected, the fix is usually in the beta app description, review notes, entitlement setup, or some feature Apple wants explained clearly. Apple’s help pages make those fields part of the external testing setup, which is why the review can stall on missing or unclear information instead of on the code itself. That is annoying, but it is the process Apple documents for external testing.

The short version is simple. Yes, the review rules changed in the sense that Apple now documents full review as required for the first build of a version, not every later build. No, external testers do not bypass review, and no, the 100 tester limit does not apply to external testers.

If you are planning your release flow, the move is to submit one clean first build, keep the review info complete, and expect later builds in the same version to be easier than the first one. That is the rule Apple documents today, and it is the rule that matters when you are trying to get external testers into a beta without wasting a day on avoidable resubmission.