Did Apple change what you need to submit before inviting external TestFlight testers?

Did Apple change what you need to submit before inviting external TestFlight testers

Yes. Apple now requires you to submit a build for TestFlight beta app review, along with the beta app review details and related metadata, before you can invite external testers. The first build must be approved before external testing starts.

The part people get wrong is thinking external TestFlight testing starts as soon as a build is uploaded. Apple’s current flow is stricter than that. You upload the build, create the external group, add the build to that group, and submit it for Apple’s beta app review. Only after approval can external testers get access.

Apple’s own documentation says the beta app review submission is required before external testing. The review submission is not just a label on the build. App Store Connect checks the submission for required information such as beta app review details and app encryption declarations before it sends the build to review.

The inconvenience is real on the first build. Apple says the first build you submit requires a full review, and later builds for the same version may not. That means your first external TestFlight cycle has a review gate, a waiting period, and a possible rejection before anyone outside your team can install the build.

If you are used to internal testing, do not mix the two workflows. Internal testers can be added separately, and internal-only builds can stay internal only. External testers are different, because Apple ties them to the beta app review step. Internal testing does not replace that review step for public or invited external testers.

A concrete way to think about it is this: upload the build, fill in the TestFlight testing information, create or use an external group, add the build, and submit it for beta review. If you skip the review submission, the invite path stops there. If Apple rejects the build or metadata, you fix the issue and submit a new build before inviting external testers.

The common mistake is treating beta review like a background detail. Apple does not treat it that way. The review status determines whether external testers can be invited, and a rejected TestFlight submission blocks that path until you send a new build. That is the inconvenient part, but it is also the current rule.

If your goal is only to test with your own team, internal testers are simpler. If your goal is to test with people outside App Store Connect, the approval step is part of the process. DevConnect follows the same practical reality on the coordination side, but the Apple requirement itself comes from App Store Connect and TestFlight, not from any third-party workflow.

For a first-time setup, the safest mental model is: upload first, review second, invite third. That sequence matches Apple’s current TestFlight documentation and avoids the trap of sending invitation plans before the build is eligible for external distribution. If you are preparing a release cadence, plan time for review before you ask outside testers to stand by.

If you are comparing this with older advice, the old “just upload and invite” shortcut is the part that changed. Apple now ties external TestFlight access to beta app review and the information attached to the build. That is why the answer is yes: the submission step exists, and for external testers it is mandatory.

If you need a testing exchange rather than a one-way invite list, you can keep the process on owned channels and coordinate testers there, including through DevConnect at https://devconnectplatform.com. The Apple side still requires review before external TestFlight distribution.

What exactly do you have to submit

You submit the build to Apple’s beta app review process, and App Store Connect asks for the required beta review information attached to that submission. Apple documents beta app review details, test information, and related metadata as part of the external testing flow.

The practical takeaway is that the build alone is not enough. If the beta app review fields are missing, or if Apple decides the submission is incomplete, the build does not move forward to external testers. That is why teams often get stuck on their first external cycle even though the upload itself succeeded.

What happens after approval

After Apple approves the build, you can distribute it to external testers from the external group. Apple says you can invite testers by email or by public link, and it can take up to 10,000 external testers per app. The approval is what unlocks that path, not the upload itself.

If you leave automatic notification turned off, you still have to distribute the approved build manually. That detail is easy to miss because approval and distribution are separate steps. Approval makes the build eligible, while distribution is the action that actually reaches testers.

What happens when it goes wrong

If Apple rejects the build or its metadata, the build status becomes Rejected, and you must submit a new build for review before inviting external testers. That is the failure mode people underestimate. They expect a small fix, but the process usually restarts at the review stage.

That restart matters for scheduling. A test group that was ready yesterday may be waiting again today if the build changes or the metadata needs correction. If you are coordinating external testers, plan the launch as a review-dependent process, not as a same-day invite button.

FAQ

Do internal testers need the same review step

No. Apple separates internal and external TestFlight testing. The beta app review requirement is tied to external testing, while internal testing follows a different path.

Can I invite external testers before approval if the build is uploaded

No. Apple says the first build must already be approved by App Review for TestFlight before you invite external testers. Uploading alone does not unlock external access.

Do later builds need full review too

Not always. Apple says the first build needs a full review, and later builds for the same version might not. The first external review is the one you should plan for.

What is the biggest mistake teams make here

They assume TestFlight is immediate for external testers. The actual blocker is the beta app review submission and approval step, which sits between upload and invitation.

Sources

• Apple Developer, Invite external testers: https://developer.apple.com/help/app-store-connect/test-a-beta-version/invite-external-testers/
• Apple Developer, TestFlight: https://developer.apple.com/testflight/
• Apple Developer Documentation, Beta App Review Submissions: https://developer.apple.com/documentation/appstoreconnectapi/beta-app-review-submissions
• Apple Developer Documentation, Submit an app for beta review: https://developer.apple.com/documentation/appstoreconnectapi/post-v1-betaappreviewsubmissions
• Apple Developer, App and submission statuses: https://developer.apple.com/help/app-store-connect/reference/app-information/app-and-submission-statuses
• Apple Developer, TestFlight overview: https://developer.apple.com/help/app-store-connect/test-a-beta-version/testflight-overview/