You uploaded a TestFlight build for external testers four days ago. Internal testers can install it immediately, but external testers see “This build is not yet available.” In App Store Connect, the build under your external group shows status Waiting for Review. Your last few reviews cleared in under a day; this one’s at 96 hours. No reviewer message, no rejection, no email — just silence. You’re wondering whether to re-upload, contact Apple, or just wait.
Fastest path: there is no expedite for TestFlight App Review, so first rule out anything silently blocking you (check Resolution Center and that the build isn’t stuck on Missing Compliance), then unblock urgent testing through internal testers (no review required) while the external review finishes. Only contact Apple after you’ve actually passed the expected window below.
As of June 2026, the median “Waiting for Review” time is roughly 9 hours and active “In Beta Review” is about 1 hour (per Runway’s live review-time tracker). But the tail is long: during high-volume windows the same queue stretches to several days, and developers reported 7 to 30 day waits during the March 2026 backlog. So a 4-day wait is slow but not yet abnormal enough to mean something is broken.
A naming note that trips people up: Apple now calls this TestFlight App Review in the docs (it was historically “Beta App Review,” and you’ll still see “In Beta Review” as a build status). Same review, same queue.
Which bucket are you in
Run down this table before doing anything. The top rows are the cheap, high-probability checks.
| Symptom | Likely cause | Where to look | Action |
|---|---|---|---|
| Build status is yellow Missing Compliance / Waiting for Export Compliance Review | Export-compliance answer pending — review hasn’t even started | TestFlight tab, build row | Answer the encryption question (see Step 1) |
| Open thread in Resolution Center | Apple is waiting on you; the clock is effectively paused | App Store Connect → Resolution Center | Reply to the thread |
| First-ever external build of a brand-new app | First-app reviews get extra scrutiny (developer history, business, content) | n/a | Expect 2-4 days; see cause 1 |
| You added an entitlement / new IAP / auth method since last build | Build flagged for human review | Diff capabilities vs last fast build | Expect slower; see cause 3 |
| WWDC week, late Nov-Dec, or just after a major iOS release | Systemic high-volume backlog | r/iOSProgramming, Apple Developer Forums | Wait; see cause 2 |
| Status already says Ready to Test but testers can’t install | UI/propagation lag | Hard-refresh; check Activity | See cause 5 |
| Nothing above fits and it’s been days | Possible system incident or genuinely slow queue | Apple System Status | See cause 6, then Step 5 |
Common causes
Ordered by hit rate.
1. First external review for a new app
The first external build of a brand-new app gets extra scrutiny: developer history, business validation, content review. Expect 2-4 days for v1.0, versus the sub-day median for an established app. Note Apple’s actual rule: the first build of each new version requires a full review; later builds of the same version often skip it. So a fresh version number, not just a fresh app, can re-trigger the longer path.
How to spot it: Check whether this is the first build of this version (or your first ever submission for this app). Either resets you to the slower lane.
2. Apple high-volume window
WWDC week (early-to-mid June), late November through December (holiday app freeze ramp-up), and the days after a major iOS release all cluster review delays. TestFlight App Review draws from the same reviewer pool as full App Store Review; it gets oversubscribed during these windows. The March 2026 backlog pushed some external reviews to 7+ days.
How to spot it: Check community sources (r/iOSProgramming, Apple Developer Forums) and the Runway tracker. If other developers report multi-day reviews in the same window, it’s systemic and waiting is the only real lever.
3. Build tripped a review heuristic
Adding entitlements (HealthKit, Contacts, push, background modes), a new sign-in/auth scheme, a new in-app purchase, or a sensitive data category all extend review. The system flags the build for closer human scrutiny.
How to spot it: Diff your entitlements, IAP configuration, and capabilities against the last build that cleared quickly. Any addition predicts a slower review.
4. Reviewer needs information you didn’t provide
The What to Test field (under Test Information) is where you tell the reviewer how to exercise the build. If your build has a non-obvious or gated feature and you didn’t explain how to reach it, the reviewer can stall looking for guidance, or bounce it to Resolution Center.
How to spot it: Read your What to Test notes. If they say “Bug fixes and improvements” but you actually shipped a new gated feature, that’s the gap. Add demo credentials and a one-line path to the feature.
5. Build is approved but the UI hasn’t caught up
Some reviews complete in the backend before the TestFlight tab refreshes. The build is Ready to Test but your group view still shows Waiting for Review for a while.
How to spot it: Hard-refresh App Store Connect (Cmd+Shift+R / Ctrl+Shift+R). Check the build’s Activity for a state-change timestamp, and watch for the approval email (Admins receive it).
6. Apple system status incident
Rare but real: a TestFlight or App Store Connect incident can park reviews silently. Apple’s system status page sometimes lags 30+ minutes before an incident is acknowledged.
How to spot it: Check both the Apple system status page and developer forums / social for “TestFlight” or “App Review” mentions in the past 48 hours.
Information to collect first
- Exact upload timestamp from App Store Connect → Activity → All Builds.
- The build’s current status string and how long it’s been in it.
- Your What to Test text.
- Whether this is the first build of this version (or your first ever submission for the app).
- Any added entitlements, IAPs, or capabilities since the last build that cleared fast.
Shortest path to fix
Step 1: Confirm the build isn’t blocked on compliance
Open App Store Connect → TestFlight → External Testing → your group, and look at the build row.
- A yellow Missing Compliance or Waiting for Export Compliance Review means review hasn’t started. Answer the export-compliance / encryption question first. (You can pre-answer it for future builds by adding
ITSAppUsesNonExemptEncryptionto yourInfo.plist.) - A green Ready to Submit that you never submitted means it was never queued — submit it for review.
- Waiting for Review (yellow) → it’s queued; In Beta Review (yellow) → a reviewer is actively on it; Ready to Test (green) → done.
Step 2: Check Resolution Center
App Store Connect → Resolution Center → open your app’s thread. Apple sometimes posts a review question here that does not send an email, and the review clock effectively pauses until you reply. An unanswered thread is the single most common “stuck for days” cause that’s actually your fault. Respond if there’s an open question.
Step 3: Unblock urgent testing with internal testers
Internal testers do not require TestFlight App Review and can install as soon as processing finishes. You can have up to 100 internal testers, and each can test on up to 30 devices. Add anyone whose testing can’t wait to the internal group so the external review isn’t a hard blocker.
App Store Connect → TestFlight → Internal Testing → Add Testers. Each internal tester must be a member of your Apple Developer Program team with a role of Account Holder, Admin, App Manager, Developer, or Marketing.
Step 4: Wait the appropriate window
Time the submission, then hold until you cross the right “contact Apple” threshold. (Medians per the Runway tracker as of June 2026; thresholds are conservative.)
| Submission timing | Typical clear | Wait before contacting Apple |
|---|---|---|
| Mon-Wed, established app | Same day to 24h | 3 business days |
| Thu-Fri, established app | 24-48h | Following Tuesday |
| High-volume week (WWDC, Dec, post-iOS) | 3-7 days | 7 business days |
| First build of a new app | 2-4 days | 5 business days |
Resubmitting an identical build usually restarts the queue rather than skipping it. Note Apple’s caps: you can submit at most 6 builds for review per 24 hours, and only one build of a given version can be in review at a time.
Step 5: Contact Apple after the wait window
Use Contact App Review and pick the TestFlight status-update topic. Keep it factual and specific:
Subject: TestFlight build awaiting review — status update request
App: Acme Studio
Build: 2.7 (47)
Submitted: 2026-05-15 14:32 PT
Current status: Waiting for Review (5 business days)
Could you confirm whether this TestFlight submission has been routed?
This is an external test cycle that other deadlines depend on.
Thank you.There is no expedited path for TestFlight App Review — do not request an expedite from this queue (expedite requests are for full App Store Review only).
Step 6: Improve What to Test for next time
Your What to Test notes should mirror good App Review notes: demo credentials, a one-line walkthrough for each new or gated feature, region-specific considerations, and a contact. Reviewers move faster when they can answer their own questions from your notes instead of stopping to ask.
How to confirm it’s fixed
- The build status moves from Waiting for Review (or In Beta Review) to Ready to Test — within hours of contacting Apple, or naturally inside the expected window.
- External testers can install the build from the TestFlight app and no longer see “This build is not yet available.”
- App Store Connect → Activity shows the state-change timestamp.
- An approval email arrives (sent to Admins).
If it still won’t clear
- Reply to your existing Contact App Review thread with the original case number — don’t open a fresh one, which sends you to the back of the line.
- Confirm via the Apple Developer System Status page that there’s no active TestFlight or App Store Connect incident.
- Upload a real new build (a genuine bug fix or small feature) — Apple sometimes prioritizes newer submissions over an identical re-upload of the same build, and a slightly different build can dodge whatever heuristic snagged the last one.
- Reassess the build’s risk profile (new entitlement, new IAP, sensitive category). If one change is consistently the long pole, split it into its own release so a single review is faster.
Prevention
- Submit the first build of a new app, or any new version, well before any external test window depends on it; assume up to 5 business days for a first review.
- Keep a What to Test template in your repo and copy from it for every external submission.
- Split risky changes (new entitlements, IAP, auth) across releases so any single review is faster.
- Pre-answer export compliance via
ITSAppUsesNonExemptEncryptioninInfo.plistso builds never park on Missing Compliance. - Keep critical testers in the Internal Testing group as a fallback — internal needs no review.
- Avoid pairing time-critical external submissions with known high-volume periods (WWDC week, December holidays, the week after a major iOS release).
Related reading
- App version stuck in Waiting for Review
- TestFlight build stuck in Processing
- TestFlight external tester no invite
- New build uploaded but not appearing
Tags: #Troubleshooting #App Store #App review #TestFlight #Beta review