Did Apple update what you need to submit before external TestFlight testing?

Did Apple update what you need to submit before external TestFlight testing

Yes. Before external TestFlight testing, Apple requires you to submit the build for TestFlight App Review and provide the beta app review information Apple asks for. The required setup now includes test information, a beta app description, and a feedback email address.

The part people get wrong is treating external TestFlight like internal testing. Internal testers can be added inside App Store Connect, but external testers are behind Apple’s review step. Apple says you must submit a new build for review before you can invite external testers, and the first build of a version is the one tied to that review gate.

Apple’s current TestFlight flow starts in App Store Connect. You open the app, go to the TestFlight tab, add the test information, upload a beta build, and then submit that build for beta app review. Apple says the beta app description is required, and the feedback email is also required for external testing.

The inconvenient part is that Apple reviews the build together with its accompanying metadata. That means a missing description, missing review details, or a mismatch between what you uploaded and what you wrote can block external testing until you fix the submission and send it again. Apple’s documentation makes clear that the beta app review submission is validated before it goes to the review team.

Apple’s help pages also show that the information is not just a one-time form. You can update the test information later, and the changes show up in TestFlight. That matters when you change what testers should focus on, when you swap a feedback inbox, or when you want to revise the invitation text before a new round of testing.

If you want the shortest practical answer, it is this: for external TestFlight testing, you need a build, beta app review details, and test information in App Store Connect before Apple lets you invite outside testers. The build is not enough on its own. The review package is what unlocks the external invite step.

A concrete example helps. Suppose you upload version 1.0 build 23, but you leave the beta app description blank. Apple’s documentation says that description is required, so the review submission is not complete. You would need to fill in the missing beta app review information, resubmit, and wait for approval before external testers can receive the invitation.

People also mix up the terms. “TestFlight” is the distribution channel, “TestFlight App Review” is the review process for external testers, and “beta app review submission” is the formal submission Apple uses for that review. When the app is approved, you can invite external testers, up to 10,000 of them, while internal testers remain separate and capped at 100 App Store Connect users.

For teams that also work with Google Play, the contrast is useful. Apple does not use Google Play’s 14-day closed-testing path for TestFlight. Apple’s external testing path is its own review-and-distribute process, and once approved, testers join through email invitation or a public link inside TestFlight.

If your goal is to keep a release moving, the safest order is simple: upload the build, fill in the beta app description and test information, submit for beta app review, then invite external testers after approval. That sequence matches Apple’s published flow and avoids the most common failure point, which is trying to invite outside testers before the review step is complete.

If you are setting up repeated testing rounds, a team-owned workflow like DevConnect can help you coordinate testers without paying for them, and without moving outside the owner’s own systems. The platform itself is at devconnectplatform.com, but Apple’s submission requirement still stays the same: external TestFlight testing starts after review, not before.

In practice, the update is not that Apple made TestFlight harder in one dramatic step. Apple made the required submission clearer and more explicit. The change that matters is that external testing now visibly depends on the review packet being complete, not just on having a build uploaded somewhere in App Store Connect.

For teams that ship often, the best habit is to treat TestFlight review copy like release metadata, not filler. Write the beta app description, set the feedback email, check the test instructions, and verify that the build you plan to share is the one you actually submitted for review. That avoids the common delay where testers are ready but Apple has not approved the build yet.