Many iOS developers assume Apple only evaluates applications during final App Store submission. However, inviting external testers (users outside your App Store Connect development organization) requires your pre-release build to pass Beta App Review. If Apple rejects the build, distribution to your external testing groups halts immediately.
Resolving a Beta App Review rejection is a hybrid workflow. Reviewer correspondence and crash logs live exclusively in Apple's web portal Resolution Center, as Apple's REST API does not expose direct reviewer chat. Once you paste the reviewer's feedback into your AI coding assistant, your assistant diagnoses the issue, helps you update your project configuration or metadata, and uses FlightDeck to verify build readiness and attach the approved build to your external beta groups.
What You Need
Before resolving a TestFlight beta rejection:
- An active Apple Developer account with access to App Store Connect.
- FlightDeck installed and connected to your App Store Connect account.
- An AI coding assistant (Cursor, Claude Code, Antigravity, Windsurf, or Roo Code) connected to FlightDeck via MCP. See Connecting Cursor to App Store Connect or Claude Code CLI Guide.
- The specific rejection notice from App Store Connect Resolution Center.
Internal Testing vs. External Testing: Review Requirements
Understanding the boundary between internal and external TestFlight groups is essential for managing release schedules:
┌─────────────────────────────────────────────────────────────────────────────┐
│ Internal Testing (Up to 100 Testers) │
├─────────────────────────────────────────────────────────────────────────────┤
│ • Audience: App Store Connect team members (Admin, App Manager, Developer). │
│ • Review Required? NO. │
│ • Availability: Accessible as soon as binary processing and export │
│ compliance clear. Builds never undergo Beta App Review. │
└─────────────────────────────────────────────────────────────────────────────┘
vs.
┌─────────────────────────────────────────────────────────────────────────────┐
│ External Testing (Up to 10,000 Testers) │
├─────────────────────────────────────────────────────────────────────────────┤
│ • Audience: External users invited by email or public invitation links. │
│ • Review Required? YES (TestFlight Beta App Review). │
│ • Availability: Blocked until Apple review staff evaluates and approves it. │
│ • Turnaround: Varies dynamically based on Apple queue depth (often up to │
│ 48 hours; Apple provides no guaranteed turnaround SLA). │
└─────────────────────────────────────────────────────────────────────────────┘
The 8-Stage TestFlight Release Lifecycle
To understand why a build is not yet available to testers, distinguish these sequential milestones:
- Build Ingestion & Processing: Apple's Transporter processes the binary archive. Processing status must reach
VALID. - Export Compliance Declaration: Compliance status must be cleared (either via
ITSAppUsesNonExemptEncryptioninInfo.plistor answering the portal questionnaire). - Internal TestFlight Eligibility: The build can immediately be installed by internal team members.
- External Beta App Review Submission: You submit the build for external review along with test notes and demo credentials.
- External Beta App Review Approval: Apple evaluates the build against safety, stability, and content guidelines until marked
In Beta Testing. - External Beta-Group Association: The approved build is linked to one or more external beta groups (
build_add_to_beta_group). - Public Invitation-Link Availability: If the group uses public links, the link activates for new tester sign-ups.
- Tester Notification & Installation: Testers receive push/email alerts through the TestFlight iOS app and can install the build.
Subsequent Builds Under the Same Version: When you submit the first build of a new marketing version (for example, version 1.2.0, build 1), a full Beta App Review is required before external distribution can begin. For Subsequent Builds Under the Same Version (such as 1.2.0 (2)), Apple's automated evaluation system may expedite review or allow distribution without a prolonged manual cycle if the binary introduces no new capabilities or entitlements. However, subsequent builds are never automatically approved. Apple explicitly reserves the right to subject any subsequent build to standard manual Beta App Review. Adding new background modes, HealthKit/Push entitlements, privacy declarations, or significant binary changes will routinely trigger a full manual review.
Build Processing vs. External Testing Approval: When your build status transitions to VALID in App Store Connect, it means only that Apple's automated binary ingestion pipeline has finished. It does not mean the build is approved for external testers. External distribution remains blocked until the build status in TestFlight specifically reflects In Beta Testing.
Practical Diagnostic Prompt: Checking Build State Across Gates
Before submitting or diagnosing a stalled build, use this prompt to have your AI assistant inspect your build's current status across Apple's delivery gates:
Inspect our latest uploaded builds for [App Name] using FlightDeck. Tell me:
1. Which build is the latest, and what is its processing state?
2. Has export compliance been cleared on this build?
3. Is it currently eligible for internal TestFlight testers?
4. What is its Beta App Review status for external testing (e.g. Unsubmitted, In Review, Approved, or Rejected)?
5. Which beta groups (internal or external) currently have this build attached?
Identify any outstanding requirements blocking external distribution.
Your assistant queries builds_list and build_beta_details_get to summarize the exact lifecycle stage and flag whether missing compliance or pending review is halting delivery.
Why Apple Rejects Beta Builds (Top 4 Causes)
Beta App Review is lighter and faster than full App Store review, but Apple enforces four primary compliance standards:
- Missing Demo Credentials or Broken Login: If your app presents a sign-in screen, the reviewer must be able to log in. Failing to provide working credentials in TestFlight's Test Information is the single most common cause of rejection. - Typical Message: "Guideline 2.1 - Information Needed. We were unable to sign in to your app to test its features."
- Immediate Crash on Launch: If the application terminates unexpectedly before the initial screen renders on physical hardware, reviewers reject the build immediately and attach crash logs (
.ipsfiles). - Typical Message: "We discovered one or more bugs in your app when reviewed on iPad running iPadOS 18. Specifically, the app crashed on launch."
- Missing or Incomplete Export Compliance: If your app uses non-exempt cryptography without appropriate declarations, Apple halts external distribution. - Typical Message: "Export compliance documentation required before testing can begin."
- Inappropriate or Vague "What to Test" Notes: Submitting placeholder text like
"test","bug fixes", or profanity in the tester notes triggers rejection. Apple requires clear guidance on what external testers should evaluate.
Where Reviewer Messages Live: Resolution Center
Apple's App Store Connect REST API does not provide an endpoint for human-to-human chat messages in Resolution Center. When a build is rejected:
- Log in to App Store Connect.
- Navigate to Apps > [Your App] > TestFlight > iOS.
- Select the build marked with a red Rejected status tag.
- Click Resolution Center in the banner at the top of the screen.
- Review the specific notes, tested device model, and any attached crash logs or screenshots.
Because this correspondence cannot be read directly over the API, you simply copy the reviewer's message from Resolution Center and paste it into your AI coding assistant.
Step-by-Step Remediation Workflow
Follow this hybrid sequence to diagnose, resolve, and distribute your beta build.
flowchart TD
A["Step 1: Check Resolution Center (Manual)"] --> B["Step 2: Paste Rejection into AI Chat (Prompt)"]
B --> C{"Is it a Code Defect or Metadata Issue?"}
C -->|"Metadata / Credential Issue"| D["Step 3A: Update Test Information in Portal"]
C -->|"Crash / Code Bug"| E["Step 3B: Fix Code, Bump Build & Re-Upload"]
D --> F["Step 4: Distribute to Beta Group via FlightDeck (Prompt)"]
E --> F
F --> G["Step 5: Verify Remote Distribution (Prompt)"]
Step 1: Diagnose the Rejection with Your AI Assistant
Copy the text from Resolution Center and prompt your assistant:
Apple's TestFlight Beta App Review rejected our latest build for [App Name]. Here is the note from Resolution Center:
"[Paste reviewer message here]"
Please analyze this rejection. Tell me whether this requires a new compiled binary upload or if we can resolve it by updating Test Information in App Store Connect. If code changes are needed, guide me through fixing the defect.
Your assistant analyzes the message:
- For Informational Rejections (Demo Credentials, What to Test, Compliance): No rebuild is necessary. You update the fields directly in the App Store Connect portal, reply to the reviewer, and wait for approval.
- For Binary Defects (Crashes, Broken APIs, Missing Entitlements): You fix the issue in your codebase, increment
CFBundleVersion, build a fresh archive, and upload it to App Store Connect.
Step 2: Implement the Fix
If Fixing Demo Credentials:
- In App Store Connect under TestFlight > Test Information, enter valid credentials in Sign-In Information.
- Explain test accounts, static 2FA bypass codes, and sample data in the Review Notes field.
- Reply to the reviewer in Resolution Center indicating the credentials have been added.
If Fixing a Crash or Code Defect:
- Fix the bug identified in the crash log.
- Increment your build counter (e.g., from
42to43). - Compile and deliver the new archive to App Store Connect (see Uploading iOS IPAs Without Xcode).
Step 3: Attach the Approved Build to Your Beta Group
Once Apple approves the build for external testing (or once a subsequent build clears automated ingestion), instruct your AI assistant to attach it to your external beta testers:
Check the latest builds for [App Name] in App Store Connect. Confirm that our latest build has finished processing and is ready for beta testing. If it is ready, attach it to our external beta group named "[External Beta Group Name]".
What Your Assistant Does Behind the Scenes:
- The assistant queries App Store Connect using FlightDeck's
builds_listto find the most recent build and inspect its processing state. - It checks external beta details using
build_beta_details_getto ensure the build has cleared Beta App Review. - It stages a request to attach the build using
build_add_to_beta_group.
FlightDeck Desktop Approval Center:
Because adding a build to an external beta group publishes software to external users, FlightDeck halts execution and opens a confirmation sheet in the Desktop Approval Center:
Illustrative representation of the FlightDeck Approval Center sheet:
┌────────────────────────────────────────────────────────────────────────┐
│ FlightDeck Desktop Approval Center │
├────────────────────────────────────────────────────────────────────────┤
│ Operation: Attach Build to External Beta Group │
│ App: FocusPulse (ID: 6471234567) │
│ Build Version: 1.2.0 (Build 43) │
│ Target Beta Group: "VIP Beta Testers" (External) │
│ Reason: Distribute post-review hotfix build to external testers │
│ │
│ [x] Build export compliance cleared │
│ [x] Beta App Review status: APPROVED │
│ │
│ [ Reject ] [ Approve & Commit ] │
└────────────────────────────────────────────────────────────────────────┘
Review the build number and target group, then click Approve & Commit. FlightDeck completes the association and notifies your AI assistant.
Verify Success: Confirming Remote Distribution
Once approved, instruct your assistant to verify that the build is actively distributed:
Query App Store Connect for [App Name] and verify that build [43] is now active in the "[External Beta Group Name]" beta group. Confirm whether external testers have received distribution notifications.
Your assistant queries the beta group's build associations. External testers will receive an update notification through the TestFlight iOS app or via email.
Emergency Detachment: Retracting a Faulty Build
If external testers report a critical issue after distribution, you can retract the build immediately without visiting the web portal:
Testers are reporting an unexpected crash in build [43] of [App Name]. Please remove this build from the "[External Beta Group Name]" external beta group immediately to halt new installations.
Your assistant stages a build_remove_from_beta_group request. Confirm the detachment in the FlightDeck Desktop Approval Center to revoke access instantly.
Troubleshooting Common Issues
1. Build Shows "Ready to Submit" Instead of "In Beta Testing"
- Cause: When you first add an external group to a build of a new marketing version, the build enters a
Ready to Submitstate requiring formal submission to Beta App Review. - Fix: In App Store Connect under the build's TestFlight tab, click Submit for Beta App Review. Turnaround is usually 12 to 24 hours.
2. "Missing Compliance" Badge Blocks External Testing
- Cause: Apple detected encryption algorithms in the binary without an export compliance declaration.
- Fix: Add
<key>ITSAppUsesNonExemptEncryption</key><false/>to yourInfo.plistfor future builds, or click Provide Export Compliance Information on the existing build in the portal. See Fixing Missing ITSAppUsesNonExemptEncryption.
3. Reviewer Cannot Bypass Two-Factor Authentication (2FA)
- Cause: The demo account sent an SMS challenge to an internal team phone.
- Fix: Provide credentials for an account configured with static OTP codes (e.g.,
123456) or temporarily disable SMS-based 2FA for the reviewer account.
Related Guides
- Automating TestFlight Beta Distribution from Your AI Coding Assistant
- Sharing Your Pre-Release App with Friends: TestFlight External Testing Setup
- Fixing TestFlight Builds Stuck in "Processing" State
- How to Retract or Expire a Broken TestFlight Build Immediately
- Pre-Flight App Store Submission Readiness Check