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.” App Store Connect’s TestFlight tab shows the build under your group with status Waiting for Review. Your last few Beta reviews cleared in 24 hours; this one’s at 96. No reviewer message, no rejection, no email — just silence. You start questioning whether you should re-upload, contact support, or just wait.
Beta App Review has no published SLA. Apple does promise it’s “typically faster” than App Store Review but won’t commit to a number. The reality: Beta review tends to clear in 1-2 days, but stretches to 4-7 days during high-volume windows or when your build trips a heuristic. What you can do is constrained — there’s no expedited path for Beta — so the play is to verify nothing is silently waiting on you, then choose between waiting and escalating.
Common causes
Ordered by hit rate.
1. First external Beta 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-3x your team’s typical Beta turnaround for v1.0. Subsequent builds of the same app are much faster.
How to spot it: Check whether this is your first ever Beta review submission for this app, not just for this version. If yes, expect longer.
2. Apple high-volume window
WWDC week (early June), late November through December (holiday gating), or the days after a major iOS release all cluster Beta review delays. Apple’s reviewer pool is the same pool that does App Store reviews; it gets oversubscribed during these windows.
How to spot it: Check community sources (r/iOSProgramming, Apple Developer Forums). If other developers report 4-7 day Beta reviews in the same window, it’s systemic.
3. Build flagged a heuristic
Adding entitlements (HealthKit, ContactsAccess, push), a new auth scheme, a new IAP, or a sensitive category change all extend Beta review. The system flags the build for human scrutiny.
How to spot it: Diff your entitlements, IAP configuration, and capabilities against the last build that cleared Beta quickly. Any addition predicts a slower review.
4. Reviewer needs information you didn’t provide
Apple’s Beta App Review form takes “What to Test” notes. If your build has a non-obvious feature that needs setup, and you didn’t explain how to test it, the reviewer may pause to look for guidance.
How to spot it: Read your Beta “What to Test” notes. If they say “Bug fixes and improvements” and you actually added a new gated feature, you need more detail.
5. Build is in Beta Review queue but Apple hasn’t displayed status update
Some Beta reviews complete in the system but the UI takes hours to refresh. The build is approved but your TestFlight tab still says Waiting.
How to spot it: Hard-refresh App Store Connect (Cmd+Shift+R). Check Activity → All Builds for a state-change timestamp.
6. Apple system status incident
Rare but real: TestFlight or App Store Connect outages can park Beta reviews silently. Apple’s system status page sometimes lags by 30+ minutes before an incident is acknowledged.
How to spot it: Check both the Apple system status page and developer Twitter / forums for “TestFlight” or “Beta Review” mentions in the past 48 hours.
Information to collect
- Exact upload timestamp from App Store Connect → Activity.
- The build’s current status and any “Waiting for Review” duration.
- Beta “What to Test” notes text.
- Whether this is the app’s first external Beta review.
- Any added entitlements, IAPs, or capabilities since the previous accepted build.
Shortest path to fix
Step 1: Verify the build’s Beta review state
In App Store Connect → TestFlight → External Testing → your group:
- Status: should be “Waiting for Beta App Review” (or “In Review” once started).
- “What to Test” text: should be present and informative.
- Build expires in 90 days (Beta has a hard lifetime).
If the status is “Missing Compliance” or similar, fix that first (the queue is paused).
Step 2: Check Resolution Center
App Store Connect → Resolution Center → look at your app’s thread. Sometimes Apple sends a Beta-specific question that doesn’t trigger an email. Respond if there’s an open question.
Step 3: Use internal testing to unblock immediate needs
Internal testers (up to 100 people on your team) do not require Beta App Review. They can install the build immediately after processing completes. Add critical testers to the internal group so testing isn’t blocked while external review pends.
App Store Connect → TestFlight → Internal Testing → Add tester. The user must be an Apple Developer Program team member.
Step 4: Wait the appropriate window
| Submission day | Median wait | Wait before contacting Apple |
|---|---|---|
| Mon-Wed | 24h | 3 business days |
| Thu-Fri | 24-48h | Following Tuesday |
| High-volume week | 3-5 days | 7 business days |
| First-ever Beta | 2-4 days | 5 business days |
Resubmitting without changes typically restarts the queue, not skips it.
Step 5: Contact Apple after the wait window
Use Contact App Review → choose “Status update on TestFlight”:
TestFlight build awaiting Beta App Review
App: Acme Studio
Build: 2.7 (47)
Submitted: 2026-05-15 14:32 PT
Current status: Waiting for Beta App Review (5 business days)
Could you confirm whether this Beta submission has been routed?
This is an external test cycle critical for [specific reason].
Thank you.There is no Expedited Beta Review; do not request expedite from the Beta queue.
Step 6: Improve “What to Test” notes for next time
Beta notes should mirror App Review notes structure: demo credentials, walkthrough for new features, regional considerations, contact info. Reviewers move faster when they can answer their own questions from your notes.
How to confirm the fix
- Status transitions from “Waiting for Beta App Review” to “Ready to Test” within hours of contacting Apple, or naturally within the expected window.
- External testers can install the build via the TestFlight app.
- App Store Connect → Activity log shows the state transition.
- Email arrives confirming Beta review outcome.
If it still fails
- Reply to your Contact App Review thread with the original ticket number; do not open a new one.
- Confirm via Apple Developer System Status that there’s no current TestFlight incident.
- Re-upload a real update (bug fix or small feature) — Apple sometimes prioritizes newer Beta submissions over identical re-uploads of the same build number.
- Consider whether your build’s risk profile (new entitlement, new IAP, sensitive category) is the systemic cause and whether splitting the change is appropriate next release.
Prevention
- Submit the first build of a new app well before any external test window depends on it; assume 5 business days for first Beta.
- Maintain a “What to Test” template in your repo; copy from it for every external Beta submission.
- Split risky changes (new entitlements, IAP, auth) across releases so any single Beta review is faster.
- Add critical testers to the internal Testing group as a backup; internal needs no Beta review.
- Avoid pairing Beta submissions with high-volume periods (WWDC week, December holidays).
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