Overview: Checking Uploaded Build Status Instantly
After uploading a new iOS archive from Xcode, Fastlane, Flutter, or FlightDeck, developers traditionally spend 10 to 30 minutes repeatedly refreshing the App Store Connect web portal, waiting to see if Apple's automated processing has finished.
With FlightDeck connected to your AI coding assistant (Cursor, Claude Code, Antigravity, Windsurf, or Roo Code), you can bypass manual web refreshes entirely. Instead, issue a single natural-language command to your assistant:
"Check the status of my latest build for [App Name] in App Store Connect. Tell me if it's finished processing and whether it's ready for TestFlight."
Your assistant queries FlightDeck's Model Context Protocol (MCP) server, inspects the active build records, and provides an instant, structured breakdown of processing status, export compliance requirements, and distribution eligibility.
This guide explains how build state inspection works, outlines the key data fields returned by Apple's API, provides copyable prompts for various testing workflows, and details how to verify status in the web portal.
1. How FlightDeck Inspects Build Processing State
FlightDeck provides dedicated, read-only MCP tools to query build records without requiring manual portal navigation or risky mutations:
+-----------------------------------------------------------------------------------+
| BUILD STATE INSPECTION WORKFLOW |
+-----------------------------------------------------------------------------------+
| |
| [DEVELOPER IN IDE] |
| "Check if build 42 of MyApp has finished processing in App Store Connect." |
| │ |
| ▼ |
| [AI CODING ASSISTANT] |
| Calls FlightDeck MCP tools: |
| 1. `builds_list(appId: "...", limit: 5, sort: "-uploadedDate")` |
| 2. `build_beta_details_get(buildId: "...")` |
| │ |
| ▼ |
| [APPLE APP STORE CONNECT API] |
| Returns build attributes: |
| - processingState: "PROCESSING" | "VALID" | "FAILED" | "INVALID" |
| - internalBetaState: "MISSING_EXPORT_COMPLIANCE" | "READY_FOR_BETA_TESTING" |
| - externalBetaState: "BETA_APPROVED" | "WAITING_FOR_REVIEW" |
| - expirationDate: 90-day ISO 8601 timestamp |
| │ |
| ▼ |
| [STRUCTURED RESPONSE TO DEVELOPER] |
| "Build 42 (1.2.0) is VALID. Export compliance is attested. |
| Ready for internal testing. External testing requires What to Test notes." |
| |
+-----------------------------------------------------------------------------------+
Key Tools Involved:
builds_list: Returns recent builds for your App ID, sorted chronologically. Exposes marketing versions, build numbers, upload dates, processing states, and assigned beta groups.build_beta_details_get: Deeply inspects TestFlight distribution states, evaluatingisEligibleForInternalTesting,isEligibleForExternalTesting, andisMissingExportCompliance.build_get: Retrieves full build metadata including minimum iOS system versions, asset tokens, and localization records.
2. Deciphering App Store Connect Processing States
When Apple ingests an uploaded binary, it transitions through distinct processing states:
| Processing State | Meaning | TestFlight Eligible? | Next Required Action |
|---|---|---|---|
PROCESSING |
Apple cloud workers are decompressing, scanning Mach-O symbols, compiling asset catalogs, and generating App Thinning slices. | NO | Wait. Apple API does not allow canceling or modifying builds in this state. |
VALID |
Processing completed with zero ingestion errors. Binary is structurally compliant. | YES (Subject to gates) | Check export compliance and assign to internal/external beta groups. |
MISSING_EXPORT_COMPLIANCE |
Binary is VALID, but distribution is paused until encryption documentation is attested. |
NO | Set ITSAppUsesNonExemptEncryption in Info.plist or answer questions in portal. |
READY_FOR_BETA_TESTING |
Fully approved for internal testing. Internal testers can install immediately without Apple review. | YES (Internal) | Add build to an internal beta group via build_add_to_beta_group. |
IN_BETA_TESTING |
Actively assigned to at least one beta group with active testers. | YES | Testers can download and submit feedback. |
FAILED or INVALID |
Ingestion rejected. Common causes: corrupted archive, invalid signature, or prohibited private APIs. | NO | Check Apple developer account email for ITMS rejection codes. Increment build and re-upload. |
Downstream Distribution Architecture: Prerequisites vs. Optional Mechanisms
A VALID Build Is Not Automatically Available to Testers: A processing state of VALID confirms only that Apple's automated cloud ingestion scanned your archive without structural errors. However, a valid build is not instantly installable on tester devices. To avoid premature release assumptions, distinguish among mandatory prerequisites, conditional gates, and optional distribution mechanisms:
+-----------------------------------------------------------------------------------+
| DOWNSTREAM TESTFLIGHT DISTRIBUTION PATHWAYS |
+-----------------------------------------------------------------------------------+
| |
| [UPLOAD COMPLETED] ───> [PROCESSING] ───> [VALID] |
| │ |
| [MANDATORY: EXPORT COMPLIANCE ATTESTATION] |
| (Info.plist or App Store Connect declaration) |
| │ |
| ┌───────────────────────┴───────────────────────┐ |
| ▼ ▼ |
| [INTERNAL TESTING TRACK] [EXTERNAL TESTING TRACK] |
| - Max 100 internal team members - Max 10,000 external testers|
| - NO Beta App Review required - CONDITIONAL GATE: |
| │ Beta App Review required |
| │ for 1st build of version |
| │ │ |
| ▼ ▼ |
| [MANDATORY: GROUP ASSIGNMENT] [MANDATORY: GROUP ASSIGNMENT]|
| build_add_to_beta_group build_add_to_beta_group |
| │ │ |
| ▼ ▼ |
| [TESTER ENROLLMENT: DIRECT] [TESTER ENROLLMENT CHANNELS] |
| Apple ID / Team Account - Direct Email Invitation OR |
| │ - OPTIONAL: Public Link Join |
| │ │ |
| └───────────────────────┬───────────────────────┘ |
| ▼ |
| [AVAILABLE IN TESTFLIGHT APP] |
| Testers can launch and install. |
| (OPTIONAL: Push notification alert dispatched; |
| delivery failure does not prevent app install) |
| |
+-----------------------------------------------------------------------------------+
1. Mandatory Prerequisites (Hard Blockers When Unmet)
These requirements strictly prevent any tester from downloading or installing the build:
- Build Processing State (
VALID): Automated asset compilation and Mach-O checks must finish with zero ingestion errors. - Export Compliance Attestation: Encryption status (
usesNonExemptEncryption) must be confirmed either via<key>ITSAppUsesNonExemptEncryption</key><false/>inInfo.plistor attested in App Store Connect. - Beta Group Association: The build must be explicitly assigned to at least one active beta group using FlightDeck's
build_add_to_beta_group. An unassigned build is invisible in TestFlight. - Tester Enrollment: Testers must be members of the assigned group (either invited by email address or joined via a public invitation link).
2. Conditional Prerequisites (Workflow-Dependent)
These requirements apply only to particular configurations:
- Beta App Review Approval (External Groups Only): The first build of a new marketing version (e.g.,
2.0.0) submitted to external beta groups must be evaluated and approved by Apple review staff. Subsequent builds in the same minor version sequence often bypass manual review. Internal groups (up to 100 team members) NEVER require Beta App Review. - What to Test Notes: Required by Apple before submitting a build for external Beta App Review or adding builds to external groups, but optional for internal testing.
3. Optional Distribution Mechanisms (Non-Blocking)
These features facilitate onboarding but are never universal requirements:
- Public Invitation Links: An optional enrollment mechanism for community testing. If developers invite testers via email addresses, public links are completely unnecessary.
- TestFlight Push Notifications: Operating system notifications inform testers when a new build is available. However, successful push-notification delivery is not required for installation—testers can open the TestFlight app at any time and install or update an available build directly from their app list.
3. Copyable Natural-Language AI Prompts
Use these prompts in your AI coding assistant. They require no raw JSON or obscure identifiers—your assistant handles API interaction autonomously:
Prompt 1: Checking Your Latest Build Status
Using FlightDeck, check the status of our newest uploaded build for [App Name] on iOS.
Please provide a concise summary:
1. Version string and build number (e.g., 1.2.0 build 42).
2. Upload date and timestamp.
3. Current processingState (e.g., PROCESSING, VALID, or FAILED).
4. TestFlight eligibility: is it ready for internal testing? Does external testing require Beta App Review or What to Test notes?
5. Any visible blockers (such as missing export compliance or validation warnings).
Do not make any modifications to App Store Connect.
Prompt 2: Comparing Recent Uploads
Using FlightDeck, list the last 3 builds uploaded for [App Name].
For each build, show:
- Build number and marketing version
- Processing state
- Assigned beta groups (if any)
- Expiration date
Tell me which build is currently recommended for active beta testing. Do not stage or execute any changes.
4. Manual Web Portal Verification Steps
If you need to verify build processing status manually in Apple's web dashboard:
- Log in to appstoreconnect.apple.com.
- Click My Apps and select your application.
- Click the TestFlight tab in the top navigation bar.
- Under the iOS Builds section in the left sidebar, locate your build number: - A blue spinning indicator: The build is actively
PROCESSING. - A yellow warning triangle: The build isVALIDbut requires export compliance (MISSING_EXPORT_COMPLIANCE). Click Manage next to the warning to provide the encryption declaration. - A green checkmark or build row: The build isREADY_FOR_BETA_TESTING. - A red exclamation badge: The build failed processing. Hover over the badge to inspect the rejection reason.
+-------------------------------------------------------------------+
| APP STORE CONNECT PORTAL PATH |
+-------------------------------------------------------------------+
| App Store Connect |
| └── My Apps |
| └── [Your App] |
| └── TestFlight (Tab) |
| └── iOS Builds (Sidebar) |
| └── [Build Number] -> Status Indicator |
+-------------------------------------------------------------------+
5. Security and Governance Rules
Checking build status in FlightDeck follows strict safety protocols:
- Strictly Read-Only: Tools like
builds_listandbuild_beta_details_getperform HTTPGETrequests against Apple's REST API. They cannot alter live metadata, assign testers, or delete records. - Autonomous Execution: Because query operations are read-only, they execute immediately without triggering approval cards in the FlightDeck Approval Center.
- Credential Protection: FlightDeck uses local loopback (
http://127.0.0.1:51122/mcp) and signs JSON Web Tokens locally. Your App Store Connect API keys are never exposed in prompt text or transmitted across external servers.