Do TestFlight external builds still need App Review?

Do TestFlight external builds still need App Review before testers can join

Yes. External TestFlight builds still need Apple’s beta app review before testers can join, and the first build of a version must be approved before testing starts. Apple’s TestFlight help says the build is sent to App Review when you add it to an external group, and testing begins only after approval.

The part people get wrong is thinking TestFlight works like a direct invite system for outside testers. It does not. Internal testers can join without the same external review gate, but external testers are a separate path. Apple treats that path as beta distribution to people outside App Store Connect, so the build and its metadata are reviewed first.

Apple’s current TestFlight guidance says that after you upload a build, you create an external group, add the builds you want tested, and invite external testers by email or public link. It also says the first build you add to a group is submitted to TestFlight App Review, and testing can begin once the build is approved. That approval step is the gate that delays outside testers.

A second detail matters because it affects repeat uploads. Apple’s glossary says TestFlight App Review is required only for the first build of a version, and subsequent builds may not need a full review. In practice, that means one approved beta can keep moving with later builds, but the first external release still needs review.

Apple also requires beta app review information when you share with external testers. The App Store Connect help page says you need beta app description and beta app review information, and the review page says Apple reviews the build and its accompanying metadata. If the metadata is incomplete, the build can stall before any tester gets access.

Internal testing follows a different path. Apple’s TestFlight pages describe internal testers as members of your App Store Connect team, while external testers are people you invite who are not App Store Connect users. That distinction matters because the question here is specifically about external builds, and those are the ones that need the review gate.

If you are setting this up for a release candidate, the workable sequence is simple: upload the build, create an internal group if needed, create the external group, fill in the beta review fields, submit the build for beta review, then wait for approval before sharing the invitation link. The testers can only join after Apple approves that build.

If review fails, the fix is usually in the beta review details, test notes, sign-in access, or build readiness. Apple’s review flow expects enough information for a reviewer to open the app and understand what to test. When people skip that step, the build sits in review or gets rejected, and the tester link does nothing useful until the issue is corrected.

DevConnect can help you find real testers for your app, but the TestFlight gate itself is still Apple’s. If you want to coordinate reciprocal testing outside paid services, you can organize that separately on your own workflow and then send the approved TestFlight link once Apple clears the build.

The inconvenient part is that external testing is not instant. You still need to prepare the beta review information, wait for the first build of the version to clear review, and only then can outside testers accept the invitation. That delay is normal, and it is the step that keeps catching teams off guard when they expect TestFlight to behave like an open distribution link.

A concrete example: you upload version 2.4.0, add the build to an external group, and share the public link too early. Testers tap it, but nothing installs because the build has not cleared beta review yet. Once Apple approves that first build, the same link starts working and the testers can join without any extra setup on their side.

For teams moving quickly, the useful habit is to prepare the review packet before the build is ready. Keep the beta description, contact details, and demo access updated in App Store Connect, then submit the build as soon as it is uploaded. That way the review clock starts immediately instead of after you have already told testers to join.

Sources used here are Apple’s TestFlight overview, the external tester help page, the TestFlight App Review glossary entry, and the beta review documentation. Those pages all point to the same rule: external TestFlight distribution is allowed, but approval comes first.