skip to content

In TestFlight, why does a ski-resort app's first external build wait for TestFlight App Review when the internal QA group already has it?

level: middleimportance: should knowfreq 38%

answer

  1. internal needs no review
  2. first build gets the full review
  3. the build and its test information
  4. one build per version in review
  5. Automatically notify testers left unticked

basics

~20 s

Internal groups can test a build as soon as it is Ready to Submit, but the first build added to an external group goes to TestFlight App Review, which checks the build and its test information before external testers can install it.

solid answer

~50 s

TestFlight treats the two tiers differently. A build whose status is **Ready to Submit** can already go to internal testers. External testers are the public, so the first build you add to an external group is submitted to **TestFlight App Review**, which reviews the build and its metadata (the Beta App Description, feedback email and contact details) against the App Review Guidelines. Its status moves through **Waiting for Review** and **In Beta Review**; only after approval can external testing begin. The first build needs a full review, while later builds of the same version might not. Only one build of each version can be in review at a time, and you can submit up to six builds in 24 hours. If *Automatically notify testers* was left off, an approved build waits at Ready to Test until you click **Notify Testers**.

go deeper

for a junior

Know that internal testers get builds without review and that external testers wait for TestFlight App Review on the first build.

for a middle

Explain the statuses from Ready to Submit to Testing, the full first review, the one-in-review-per-version rule and the six-per-day cap.

for a senior

Diagnose a stalled round: missing test information, a rejection that needs a new upload, or an approved build nobody notified testers about.

for a principal

Build review time into the beta calendar: the first external build of each version may take a full review, so ship it to external groups early.

## The scenario A ski-resort app has an internal QA group that installs every build within minutes of upload. The team now adds the same build to a new external group of season-pass holders, and nothing reaches them: the build sits in review. Nothing is broken. TestFlight is doing what it does for every first external build. ## Why the tiers differ **Internal testers** are App Store Connect users with access to your content. A build whose status is **Ready to Submit** "can be distributed to internal testers", so QA gets it without Apple looking at it. **External testers** are people outside your team, up to 10,000 per app. When you add the first build of your app to an external group, App Store Connect sends it to **TestFlight App Review** to make sure it follows the App Review Guidelines. Apple reviews the build **and its accompanying metadata**, not the binary alone. ## What the review needs from you The review reads the **test information**, so missing fields hold it up: - **Beta App Description**: required, a description of the beta. - **Feedback Email**: where testers reach you from the TestFlight app, and the reply-to of invitation emails. - **Contact information**, which the help pages ask you to enter if the Test Information dialog does not already have it. - the **What to Test** notes you enter when adding the build to the group. Managing an external group and submitting for review needs the Account Holder, Admin or App Manager role. ## The statuses a reviewed build passes through | Status | What it means | |---|---| | Ready to Submit | internal testers can have it; it can be submitted for external review | | Waiting for Review | submitted to TestFlight App Review; must be approved before external testing | | In Beta Review | being reviewed now | | Rejected | rejected by review; can no longer be used in TestFlight | | Ready to Test | testable, but no testers notified yet | | Testing | at least one group or tester is testing it | When Apple approves the build, users with the **Admin** role get an email. If it is rejected, the details are under **App Review** in the sidebar, and a rejected build cannot be fixed in place: you upload a new build. To dispute a rejection you contact TestFlight App Review. ## Rules on what gets reviewed and how often 1. **The first build needs a full review.** The help pages say later builds for the same version might not, so a lighter check is possible but not promised. 2. **One build of each version in review at a time.** You submit the next one after the current one is approved. 3. **Up to six builds** can be submitted to TestFlight App Review within a 24-hour period. 4. A build that uses Apple-hosted asset packs needs the asset packs required for testing submitted after the build. ## After approval If you ticked **Automatically notify testers** when adding the build, testers are notified once it is approved. If you left it off, the build waits at **Ready to Test**: go to the build list, choose the version and click **Notify Testers**, and the status changes to **Testing**. Testers then get a notification directing them to the TestFlight app. ## A checklist before submitting 1. Test Information filled in: Beta App Description, Feedback Email and contact details. 2. What to Test notes written for this build, localized if your testers need it. 3. Automatically notify testers ticked, unless you want to release the build to testers by hand. 4. No other build of the same version already in review. ## What to take away - Internal testing is immediate and unreviewed; external testing starts with Apple's beta review. - Plan for the first build of each external round to take review time, and do not assume the next one skips it. - Keep the test information complete before you submit, because the reviewer reads it with the build. - An approved build that nobody received is usually a notification you never sent, not a review still running. Automating the upload and the wait for processing from a lane is a separate lesson; the review itself, and what it holds back, belong to TestFlight.

  • A build was approved but external testers received nothing; what do you check?
    Whether Automatically notify testers was ticked when the build was added to the group. If it was left off, the approved build sits at Ready to Test until someone opens the build list, chooses the version and clicks Notify Testers; the status then changes to Testing and testers are notified.
  • What do you do when TestFlight App Review rejects a beta build?
    Read the rejection details under App Review in the sidebar. A rejected build can no longer be used in TestFlight, so you fix the cause, upload a new build and submit that one. If you believe the rejection is wrong, you can appeal by contacting TestFlight App Review.

Like a venue that lets staff walk in with their badge but makes the public queue at a ticket check: the first night is a full check, regulars may move faster, and the doors still open only when someone announces them.

  • Internal testers also wait for TestFlight App Review.
  • Every external build is guaranteed the same full review as the first.
  • TestFlight App Review looks only at the binary, never the test information.
  • Several builds of one version can sit in beta review at once.
  • A rejected beta build can be edited and resubmitted without a new upload.