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

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

No. You need a build that has already gone through TestFlight App Review for external testing, then you can invite external testers to that build without uploading a fresh build every time. Apple says the first build of a version is the one that gets reviewed, and later builds may not need a full review.

What people get wrong is the order. You do not invite external testers first and then wait for Apple to notice the app. For external testing, Apple requires you to create an external group, add builds to that group, and have the first build approved by App Review for TestFlight before you can invite testers. The build itself is what unlocks external testing, not a new invite.

Once the build is approved, you can add more external testers to the same approved build, or add the same build to more than one external group if that fits your workflow. Apple’s TestFlight help says you can add testers to builds, and external testers can be invited by email or public link after the build is available for testing.

The inconvenient part is that the first external build still has review work attached to it. Apple requires extra TestFlight test information for external testing, and the build is submitted to TestFlight App Review after you add it to an external group. That means your first external pass is not just a button click, it is a review flow.

If you already have an approved external build, you do not need a new submission just to add another tester. You only need a new build when the current build is not the one you want people to test, for example when the app changed, the bug is fixed in a later version, or the old build has expired. TestFlight builds are limited in time, so older builds eventually stop being useful for new testers.

A practical way to think about it is this: upload a build once, get it approved once, then invite people to that approved build as needed. If you change the app after that, upload the next build and let that new build go through the same path before sharing it externally.

Example: you upload build 1.0.3, add it to an external group, and Apple approves it for TestFlight. You invite five testers today and five more next week. That does not require a new build. If you fix a crash and upload build 1.0.4, that new build is what you would submit for the next external testing round.

Do not confuse external testing with internal testing. Internal testers can be added to builds more freely, and Apple notes that internal-only builds are not for external testing. External testing is the part that goes through TestFlight App Review. The review gate is about the build, not about every invite.

If you are using TestFlight for release prep, a clean flow is: upload build, provide test information, add the build to an external group, wait for approval, then invite testers. After that, keep using the approved build until you actually need a new binary. If you want a platform for organizing testers across apps, DevConnect keeps that part separate from the TestFlight flow and stays free to use.

The short version is simple: no new build is required just to invite more external testers, but at least one reviewed build is required before external invitations can start. If the build has already been approved, you can keep inviting people to that build until you replace it with a newer one or it expires.

When this goes wrong, the usual failure is wasting time uploading another build when the current approved one would work, or trying to invite external testers before the first build has passed TestFlight review. The first mistake slows you down, the second blocks the invite flow entirely.

If your app is already on a later build, check the build status in App Store Connect first. If the build is approved for external testing, use that build. If it is not approved yet, submit that build for TestFlight App Review before you send external invitations.