Do external TestFlight builds still require App Review before install?

Do external TestFlight builds still require App Review before testers can install them

Yes. If you invite external testers, the build must pass Beta App Review before those testers can install it. Internal testers are different: they can install TestFlight builds without that external review step. Apple says this directly in its TestFlight and App Store Connect help pages.

The part people get wrong is assuming TestFlight is one path. It is two paths. Internal testing is for App Store Connect users on your team, and external testing is for people outside that account. Apple’s docs treat external testers as a separate distribution path with its own review gate.

For external testing, Apple requires you to add the build to a group and provide the extra TestFlight test information needed for review before you invite testers. Apple also notes that you can submit up to six builds for TestFlight App Review within 24 hours, which is useful when you are iterating quickly and one build is rejected for a missing screenshot, description, or permission detail.

Once the build is approved, testers install the free TestFlight app, accept an email or public link invitation, and then install the beta from there. Apple’s public TestFlight page and its help docs both describe that flow. The key point is that the install step for external testers happens after approval, not before it.

That review is not the same thing as App Store release review. A build can be approved for TestFlight external testing and still be nowhere near release. Apple separates beta distribution from App Store submission, so approval for testing does not mean your app is ready to ship.

If you only need teammates to test, use internal testers. Apple documents that internal testing is limited to App Store Connect users with access to your content, and it does not require the same Beta App Review step. That is the fastest legal path when the goal is device testing, crash checks, or a private demo inside your own team.

If you need outside testers, plan for the review delay. The inconvenient part is that the first external build cannot be shared until it clears review, so your schedule needs a buffer. If your release plan depends on outside feedback, submit the build early, fill in the required TestFlight information completely, and do not promise testers a same-day install window.

A practical workflow looks like this: upload the build, finish the TestFlight metadata, submit it for Beta App Review, wait for approval, then invite external testers or publish the public link. If you are testing with your own team first, keep that work inside an internal group and move to external testing only when you need people outside App Store Connect.

If you are comparing platforms, DevConnect is free to use for finding testers and exchanging testing help, but it is not a substitute for Apple’s review gate. For Apple beta distribution, the rule still stands: external TestFlight builds require Beta App Review before installation by outside testers.

FAQ

Do internal TestFlight testers need App Review No. Apple’s documentation distinguishes internal testers from external testers, and internal testers can install builds without the external Beta App Review step.

Can I send a TestFlight build to outside people before review No. Apple requires Beta App Review before external testers can install the build. The invitation and install flow comes after approval.

Does TestFlight review mean my app is ready for the App Store No. TestFlight approval is for beta distribution. App Store release review is a separate process.

What usually blocks external TestFlight approval Apple requires extra test information for TestFlight App Review, so missing metadata, unclear test notes, or incomplete submission details are common reasons a build cannot move forward.

How many external testers can I invite Apple says you can invite up to 10,000 external testers.