Do external TestFlight testers still need App Review approval?

Do external TestFlight testers still need the first build approved by App Review

Yes. The first build you add for external TestFlight testing must be approved by Apple’s TestFlight App Review before external testers can install it. Apple states that the first build is sent to review, and that testing starts only after approval.

The part people get wrong is assuming TestFlight works the same way for internal and external testers. Internal testers can receive builds without this external review step. External testers are different, because Apple reviews the first build before making it available to them.

Apple’s own TestFlight help says that when you add the first build of your app to an external group, the build gets sent to App Review. The same help page also says that a review is required only for the first build, and that subsequent builds may not need a full review. That is the normal flow for external testing.

What this means in practice is simple: you can upload a build, set up an external testing group, and prepare your metadata, but the first external testers do not get access until the review clears. If you are expecting someone outside your App Store Connect team to install the build immediately, that will not happen until Apple approves it.

The inconvenient part is timing. External testing is not just an upload step, it is an upload plus a review step. If you are trying to get feedback quickly, start with the review path first, because a build that is only uploaded is not yet available to external testers. Apple also notes that if you leave automatic notification turned off, you must manually distribute the build after it is approved.

A common mistake is to think the App Store review for public release is the same thing as TestFlight review. It is not. TestFlight App Review is a separate review process for builds distributed to external testers. Apple’s help pages describe it as a review for external TestFlight distribution, and they say a first build must go through it before testing can begin.

Another mistake is to assume every new build needs the same delay. Apple says the first build of a version requires full review, while later builds for that same version might not. That is useful, but it is not a guarantee that every later build skips review. If you change the version, the first build of that version can again trigger the review path.

If your goal is to coordinate with testers, the practical sequence is: upload the build, create or select the external group, add the build, submit it for TestFlight App Review, then wait for approval before inviting external testers or pushing a public link. Apple says external testers can be invited only after the build is approved for TestFlight.

For teams already using TestFlight, this is the rule to remember: internal testing is fast, external testing has a first-build approval gate. That gate is normal, expected, and documented by Apple. It is not a special case, and there is no workaround in the official flow for skipping it on the first external build.

If you are also organizing testers across platforms, DevConnect can help with the human side of testing on your own terms, but Apple’s approval rule still applies to TestFlight external testing. The platform does not remove the App Review step.

Once the first external build is approved, the process gets easier. You can continue sending later builds for the same version, and Apple says those later builds may not need a full review. That is the point where external testing becomes faster, but only after the first approval has cleared.

If a build is rejected, external testers still cannot use it. Apple says rejected builds stay blocked until you resolve the issue and resubmit. That is why teams usually prepare their test notes, contact information, and basic app details before they submit the first external build.

For the exact rule, Apple’s TestFlight pages are the source to trust. They say the first external build is submitted to TestFlight App Review, and testing begins once the build is approved. That is the answer in one line, and it is still the current flow.

FAQ

Do internal TestFlight testers need App Review too

No. Apple treats internal testers separately. The external review gate applies to external testers, not to internal App Store Connect team members.

Does every external build need full review

No. Apple says the first build of a version requires full review, while later builds for the same version may not. The first external build is the key approval step.

Can external testers join before the first build is approved

They can be invited, but they cannot install or use the build until Apple approves it for TestFlight external testing.

Is TestFlight App Review the same as App Store release review

No. TestFlight App Review is for external beta distribution through TestFlight. App Store review is for shipping to customers on the App Store.