Did Apple change TestFlight external beta review requirements?

Did Apple change TestFlight external beta review requirements for builds or testers Yes. Apple still requires TestFlight App Review before external testers can use a build, but the review burden is not the same for every build. Apple says the first build of a version goes to review, later builds for that same version may not need a full review, and external testers can be up to 10,000 people.

The part people get wrong is mixing up build review with tester count. Tester limits are one rule, review requirements are another. Apple’s TestFlight help says internal testers are limited to 100 App Store Connect users, while external testers can be up to 10,000. The external tester cap does not remove the review step, and the review step does not reduce the tester cap.

Apple’s current help pages say that when you invite external testers, you need beta app description and beta app review information for TestFlight App Review. That information is entered in App Store Connect before you distribute the app to external testers. Apple also says the build is sent for review once it is added to an external group, and testing starts only after approval.

The review process has a specific trigger. Apple says the first build of the app added to a TestFlight external group gets sent to App Review to check that it follows the App Review Guidelines. Apple’s glossary says TestFlight App Review is required for apps distributed to external testers, and it is only required for the first build of a version. That is the key change people notice, because it is not a one-review-per-build rule anymore.

The inconvenient part is that the first external build still needs clean metadata and a clear testing setup. Apple asks for a beta app description, a feedback email address, and review details. If those are missing or weak, the external test flow stalls before any tester can install the build. For teams trying to move fast, the gating issue is usually App Store Connect setup, not the upload itself.

Builds and testers are also treated differently after approval. Apple says you can upload multiple builds, start testing multiple builds at once, and manage tester participation through groups. It also says you can view tester metrics such as sessions, crashes, and feedback. That means the external beta process is not just a review form, it is a managed distribution path with group-based access and ongoing build updates.

The part that changed most in practice is how much review repeats. Apple’s current wording says the first build of a version needs review, while later builds for the same version may not require a full review. That does not mean later builds are automatic forever. If you change the version, the approval path can come back, and the external tester workflow still depends on Apple’s current TestFlight rules in App Store Connect.

A practical example makes the difference clear. If you upload version 1.0 build 1, add it to an external group, and get it approved, your next 1.0 build may move faster. If you then jump to version 1.1, do not assume the old approval covers it. The safe workflow is to treat each version as its own external release path and check the status in App Store Connect before you tell testers to install.

If you are comparing this with Google Play closed testing, do not transfer one platform’s rules to the other. Apple TestFlight and Google Play closed tests solve different problems and use different gates. DevConnect’s own closed-test workflow exists for Google Play testing exchange, but for Apple the relevant rule is TestFlight review plus tester limits, not a 14-day closed-test threshold.

For anyone setting up external testing now, the sequence is straightforward. Create the external group in App Store Connect, add the build, fill in beta app description and beta review details, then wait for approval before inviting testers. If the build is approved, the invitation can go out. If it is not approved, the build stays blocked no matter how many testers you have ready.

The safest short answer is that Apple did not remove external review, but it narrowed how often full review repeats. External testers still trigger TestFlight App Review, the first build of a version is the critical gate, and the tester limit remains separate from that gate. If you want the official setup path in one place, start with Apple’s TestFlight overview, then cross-check the review and test information pages before you upload anything. You can also compare it with DevConnect’s testing workflow at https://devconnectplatform.com if you are planning a Google Play closed-test exchange.

What counts as an external tester in TestFlight External testers are people outside your App Store Connect team who join through email or a public link. Apple limits this pool to 10,000 testers.

Does every new build need full App Review No. Apple says the first build of a version is reviewed, and later builds for that same version may not require a full review. The approval status is still checked in App Store Connect.

Do internal testers follow the same review path No. Internal testers are separate and limited to 100 App Store Connect users. The external App Review gate is the one that matters for people outside the team.

What information does Apple require before external testing starts Apple requires beta app description, beta app review information, and a feedback email address. Those details are entered in App Store Connect before you share the build with external testers.

What should I do if my build is stuck before external testing Check that the build was added to an external group, that the beta app review fields are complete, and that App Review has approved the build. If one of those is missing, testers cannot start.