What Happens After You Submit a Build to TestFlight App Review

What happens after I submit a build to TestFlight App Review

After you submit a build, Apple puts it into TestFlight App Review and checks the build together with the beta testing metadata you provided in App Store Connect. The first build of a version requires a full review, and later builds for the same version might not. If Apple approves it, you can start or continue external testing. If Apple rejects it, the build stays blocked until you fix the issue and submit again.

The first status many people see is Waiting for Review. That means Apple has received the submission, but review has not started yet. While the build is waiting, App Store Connect still lets you edit some information, but not everything. Apple’s status reference says you can change certain details and remove items from review, but you cannot edit screenshots or app previews during that phase.

Once review starts, the status changes to In Review. At that point Apple is actively checking the submission, and you can cancel it if you want to pull it back. If the build is accepted, Apple moves it forward so it can be used for external testing. If one item in a submission is accepted and another is rejected, the submission does not move forward until every item is accepted.

What happens next depends on who you are testing with. Internal testers do not need TestFlight App Review for the same path as external testers, but external testers do. Apple says you need an external group, the build added to that group, and the build approved before you can invite external testers. If you leave automatic notification off, you still need to distribute the build manually after approval.

People often miss the part that Apple reviews the metadata too. The build is not approved only on code alone. Your testing notes, contact information, and other App Store Connect fields are part of the review package. If Apple wants changes there, the build can be rejected even when the app itself is usable. Apple’s help pages also note that you can appeal a beta build rejection through TestFlight App Review details in App Store Connect.

If Apple approves the build, testers do not all receive it in exactly the same way. Testers added to an external group can get the build through the group setup you chose, and if you did not enable automatic notification, you have to push it out yourself. Apple also notes that you can submit up to six builds for TestFlight App Review in a 24-hour period, which matters when you are iterating quickly and do not want the queue to reset your workflow.

If Apple rejects the build, App Store Connect marks the status as Rejected and shows the review details. From there you either edit the rejected item and resubmit, or remove it from the submission. For TestFlight, Apple says you must submit a new build for review before you can invite external testers again. That is the part people get wrong: a rejected beta build does not become usable just because the binary uploaded successfully.

The inconvenient part is timing. Apple does not promise an instant turnaround, and forum posts from developers show that builds can sit in Waiting for Review for several days or longer. That is not official policy, but it matches real developer reports from 2026. If you are blocked on external testing, the practical move is to check that the build has complete beta review information, then wait for the status change or Apple’s rejection message.

The first build of a version is the important one. Apple’s glossary says only the first build of a version requires TestFlight App Review, while subsequent builds may not need a full review. That means the review path can feel slow on day one and much lighter after that, as long as you stay within the same version and Apple does not ask for another full pass.

If you are preparing for external testing, the safest workflow is simple. Upload the archive, fill in the TestFlight review fields completely, submit the build, and wait for the approval or rejection status before inviting external testers. If you are moving from beta testing to App Store release, Apple also says you can reuse the last build in App Store Connect for App Review after testing is complete.

If you are comparing this with other beta channels, TestFlight is a review gate, not a public file drop. Internal testing can help you verify the build is uploaded, but it does not replace the external-review step. That distinction matters when a team thinks the archive is already “in TestFlight” and assumes testers can join immediately. For external testers, the build has to clear App Review first.

If you want a place to coordinate testers while you wait, DevConnect is a separate option for organizing real exchange-based testing on your own work, and it stays free to use. That does not change TestFlight review, but it can help you line up testers once your build is approved.

FAQ

How long does TestFlight App Review take Apple does not give a fixed time in the pages retrieved here. The official status pages define the states, and real developer forum reports show that Waiting for Review can last for days. The only reliable answer is that approval is not immediate and the queue can move slowly.

Can I make changes while my build is waiting Yes, but only to certain information. Apple says some details can still be edited while a submission is Waiting for Review, while screenshots, app previews, and some metadata are locked. If you need to change something that is locked, you usually have to remove the item from review or wait for the result.

Why was my build rejected even though the app runs Because TestFlight review includes the build and the beta testing information. A working app can still be rejected if the metadata, review notes, contact information, or instructions are incomplete or unclear. Apple shows the rejection details in App Store Connect so you can fix the specific issue and resubmit.

Do later builds of the same version need the same review Not always. Apple’s glossary says only the first build of a version requires TestFlight App Review, and later builds for that version might not need a full review. That is the normal path, but Apple still controls whether a specific later build needs another pass.

Can external testers get the build before review finishes No. Apple says external testing starts only after the first build has been approved for TestFlight App Review. Internal testing is separate. If you need external testers, review approval is the gate you have to clear first.