External TestFlight testers need App Review first

Do I need to submit a new build for review before inviting external TestFlight testers

Yes. The first build you want to share with external TestFlight testers must go through App Review and be approved before you can invite outside testers. Apple says external testing starts only after a build is added to an external group and the first build has already been approved for TestFlight.

The step people miss is that internal testing and external testing are different paths. Internal testers can use builds without the TestFlight review gate, but external testers cannot. Apple’s build status guidance says a build can be ready for internal testers, or submitted to TestFlight App Review for external testing.

In practice, you upload a build, create or choose an external group in App Store Connect, enter the required TestFlight information, then submit that build for review. After approval, you can invite external testers by email or public link. Apple also says your builds are automatically sent for review once they are added to a group, and you can manually distribute them after approval if you did not enable automatic notification.

People often ask whether every new build needs a fresh review. Apple’s help pages say the first build needs a full review, and later builds for the same version might not. That means the first external release is the important gate, while later uploads can move faster once the version is already established in TestFlight.

The inconvenient part is that you cannot skip the review just because the app is unfinished or the testers are volunteers. If you want outside people, outside Apple IDs, or a public invite link to see the beta, the build still has to clear TestFlight App Review first. Apple also notes you can only have one build of each version in review at a time.

A simple example: you upload version 1.0 build 42 today, add it to an external TestFlight group, and press submit. Apple reviews the build and its TestFlight metadata. Once it is approved, you can invite your first external testers. If you later upload version 1.0 build 43, that later build may not need the same full process, but the first external build already cleared the gate.

If your goal is only to test with your own team, use internal testing first. Apple allows up to 100 internal testers and says internal and external testing are separate routes. That is the faster place to check crashes, onboarding, and obvious install problems before you wait on TestFlight review for outsiders.

If your goal is to find real testers for a closed beta, DevConnect can help with reciprocal testing on your own app-building workflow, and it stays free to use. For the Apple side, though, the rule does not change: external TestFlight testers only come after App Review approval for the build you want to share.

What to do next is straightforward. Upload the build, create an external group, fill in the TestFlight test information, submit the build, and wait for approval. If Apple rejects it, fix the build or metadata and resubmit. If Apple approves it, invite your testers and start collecting feedback through TestFlight.

Related questions

Can I invite external testers before approval? No. Apple requires the build to be approved for TestFlight before outside testers can join that build.

Do internal testers need App Review first? No. Internal testing is separate, and Apple documents it as the faster path for team members who hold App Store Connect roles.

Do later builds for the same version always need full review? Apple says the first build needs a full review, and later builds for the same version might not. The first build is the gate you have to clear before external testing starts.

What happens if Apple rejects the build? The build stays rejected in App Store Connect, and you need to fix the issue Apple points out before external testers can use it.