Overview: Understanding Build Processing and Ingestion Times
One of the most frequent questions developers ask after running xcodebuild, Fastlane, or FlightDeck is:
"My
.ipafinished uploading to App Store Connect, but it says 'Processing'. How long does Apple take, and is something wrong?"
The short answer: Apple does not provide a guaranteed Service Level Agreement (SLA), published turnaround timetable, or fixed processing window for TestFlight builds. While developers often observe automated cloud processing completing in 10 to 30 minutes under typical server conditions, processing duration varies widely based on Apple datacenter queue depth, binary size, dynamic framework linkage, asset compilation, and automated security scans.
Furthermore, no external tool—including FlightDeck—can accelerate or bypass Apple's internal ingestion pipeline. While a build is actively undergoing automated processing in Apple's cloud, Apple's API does not support canceling, expiring, or deleting the build record.
However, using FlightDeck's Model Context Protocol (MCP) server, your AI coding assistant can query Apple's API to inspect the exact processing state, verify whether missing export compliance is stalling distribution, and determine whether a build has completed processing or encountered validation errors.
This guide provides an evidence-based overview of Apple's ingestion stages, explains why processing times fluctuate, and outlines a practical diagnostic workflow using natural-language AI prompts.
1. The Stages of Apple Build Ingestion and Distribution
When you upload an application archive (.ipa or .pkg), your file enters Apple's automated cloud ingestion infrastructure. To understand where delays can occur, distinguish between the seven sequential stages of build availability:
+-----------------------------------------------------------------------------------+
| APPLE BUILD AVAILABILITY PIPELINE |
+-----------------------------------------------------------------------------------+
| |
| [STAGE 1: COMPLETED UPLOAD] |
| Binary archive bytes stream to Apple presigned chunked storage. |
| Status: Upload Complete. Apple enqueues the archive for backend workers. |
| | |
| v |
| [STAGE 2: CLOUD PROCESSING] (processingState == "PROCESSING") |
| Apple decompresses the binary and executes automated ingestion tasks: |
| - Cryptographic signature validation & entitlement verification |
| - App Thinning device variant slicing & asset catalog compilation |
| - Privacy manifest inspection (PrivacyInfo.xcprivacy) |
| - Mach-O binary symbol scanning & prohibited API detection |
| *Note: Builds cannot be canceled, expired, or deleted while in this state.* |
| | |
| +-----------------+-----------------+ |
| | | |
| v v |
| [STAGE 3A: VALIDATION SUCCESS] [STAGE 3B: VALIDATION FAILURE] |
| processingState == "VALID" processingState == "FAILED" / "INVALID" |
| Automated scans completed. Automated scan rejected the binary. |
| | Apple sends diagnostic email with ITMS |
| | error code. Must fix root cause & re-upload
| v |
| [STAGE 4: EXPORT COMPLIANCE GATE] |
| App Store Connect checks encryption declaration (ITSAppUsesNonExemptEncryption). |
| If missing, build is held with "Missing Compliance" alert until attested. |
| | |
| +---------+---------+ |
| | | |
| v v |
| [STAGE 5: INTERNAL] [STAGE 6: EXTERNAL BETA APP REVIEW] |
| Immediately available Mandatory review for 1st build of a marketing version. |
| to internal testers Apple review personnel evaluate the build. |
| upon CDN propagation. Typically requires separate review turnaround. |
| | | |
| +---------+---------+ |
| | |
| v |
| [STAGE 7: DISTRIBUTION TO TESTERS] |
| TestFlight edge servers propagate the build to tester devices. |
| Push notifications and email invites dispatched. Testers can install. |
+-----------------------------------------------------------------------------------+
| Processing State | Apple Meaning | Developer Action Required |
|---|---|---|
PROCESSING | The binary is queued or actively undergoing automated inspection in Apple's cloud. | Wait for automated processing to conclude. In this state, Apple's API does not permit canceling or deleting the build. Do not immediately upload identical duplicates; evaluate Apple system status if delays persist. |
VALID | Automated scanning, symbol processing, and App Thinning completed successfully. | Verify export compliance (Stage 4) to enable tester downloads. For external groups, ensure Beta App Review has been submitted if required. |
FAILED / INVALID | Apple detected a structural defect, entitlement violation, or prohibited symbol during automated scanning. | Check the developer email associated with your Account Holder role for specific ITMS rejection codes (e.g. ITMS-90034, ITMS-91053). Fix the underlying defect, increment CFBundleVersion, and upload a new binary. |
2. Why Do Processing Times Vary?
Because Apple does not publish fixed delivery guarantees, processing times fluctuate due to several technical and infrastructure factors:
- System-Wide Queue Load: Peak developer traffic (such as surrounding major Apple developer events, iOS beta release weeks, or global end-of-quarter shipping cycles) increases queue depth across Apple's datacenters.
- Binary & Asset Size: Larger binaries with extensive asset catalogs, high-resolution graphics, or multiple embedded dynamic frameworks require significantly more cloud compute time for App Thinning (generating custom variants for every iPhone, iPad, and Apple Silicon device model).
- Automated Static Analysis Complexity: Apple's ingestion scanners inspect Mach-O load commands, evaluate Privacy Manifests (
PrivacyInfo.xcprivacy), check Required Reason API declarations, and parse bitcode and symbol maps. - Platform Distinctions: macOS universal
.pkginstallers containing both Apple Silicon (arm64) and Intel (x86_64) slices often take longer to analyze than lightweight iOS binaries.
3. The "Hidden Gate": Processing Done vs. Distribution Readiness
A frequent source of confusion occurs when a build shows as processed in App Store Connect, but testers still cannot download it.
In Apple's pipeline, completing processing (VALID) is not the final gate for distribution:
- Export Compliance: Apple requires all pre-release builds to declare encryption usage. If your
Info.plistlacks theITSAppUsesNonExemptEncryptionkey, the build remains blocked in App Store Connect with a yellow alert: "Missing Compliance". Testers cannot install the build until this declaration is attested. - Internal Testing Eligibility: Once export compliance is attested (or declared as exempt), internal testers on your development team receive access once Apple's CDN finishes edge propagation.
- External Beta App Review: Distributing to external beta groups requires submitting the build for Beta App Review (which involves Apple review personnel and evaluates app stability and metadata). External testers cannot install the build until this review is approved.
4. Diagnosing Build Processing via AI
Rather than constantly refreshing the App Store Connect web portal, you can instruct your AI coding assistant to query FlightDeck for real-time status:
Using FlightDeck, inspect the latest uploaded build for [App Name]. Report its current processing state, whether export compliance has been resolved, and check for any visible error diagnostics. Do not stage or execute any changes. What the Assistant Does:
- Calls
apps_listto resolve yourappId. - Calls
builds_list(appId: "<appId>", limit: 5)to retrieve recent uploads. - For the latest build, inspects:
buildNumberandversion.processingState(PROCESSING,VALID, orINVALID). - Calls
build_beta_details_get(buildId: "<buildId>")to check:isMissingExportCompliance(identifies if compliance is blocking distribution).internalBetaStateandexternalBetaState. - Outputs an exact status summary and safe recommendations.
5. Practical Diagnostic and Recovery Process
If your build has remained in the PROCESSING state for an unusually long duration, avoid immediately compiling and uploading another build without investigating. Re-uploading prematurely can create duplicate processing jobs, consume upload bandwidth, and add confusion if the initial build finishes processing.
Follow this systematic diagnostic workflow:
Step 1: Check Current Build State via FlightDeck
Run the read-only diagnostic prompt above. Confirm whether the build is genuinely still in PROCESSING, or whether it has already transitioned to VALID (with missing export compliance) or INVALID.
Step 2: Check Apple System Status
Verify that Apple's developer backend is operating normally. Check the official Apple System Status page for active service disruptions or scheduled maintenance under App Store Connect or TestFlight.
Step 3: Review Developer Account Emails
When Apple's backend fails a build, it often updates the state to INVALID and sends an automated diagnostic email to the Account Holder and Admin team members containing specific ITMS error codes (e.g. ITMS-90683 for missing privacy declarations, ITMS-90034 for signature defects).
Step 4: Confirm Upload Completeness
Ensure your upload client (Xcode, altool, Fastlane, or FlightDeck) received an explicit HTTP 200 / success confirmation from Apple's upload servers. If an upload was interrupted mid-stream, Apple may keep a partial session in queue before discarding it.
Step 5: Escalate Through Official Apple Support
If a build has remained in PROCESSING through an extended period (such as exceeding 12 to 24 hours) with no status change, no error email, and no system outage reported on Apple's status page, submit a support ticket via Apple Developer Support. Include your Application Apple ID, Version, Build Number, and upload timestamp.
Step 6: Consider a Replacement Upload Only When Justified
If there is concrete evidence that the original build cannot proceed (such as confirmation from Apple Support, an INVALID state, or a documented datacenter incident that dropped in-flight ingestion tasks):
- Resolve any local configuration or packaging defects identified in earlier steps.
- Increment the build number in your project configuration (e.g. increment
CFBundleVersionfrom42to43). Apple rejects duplicate uploads with the same version and build number. - Compile a clean release archive and upload the replacement binary.
Summary of Best Practices
- Include
ITSAppUsesNonExemptEncryption: Always add<key>ITSAppUsesNonExemptEncryption</key><false/>to your app'sInfo.plist(if your app uses standard HTTPS encryption exempt from French/BIS reporting). This eliminates the manual compliance delay entirely upon upload. - Pre-Validate Binaries: Use pre-upload validation to catch missing bundle identifiers, invalid signatures, or missing icons locally before uploading.
- Plan for Beta Review: Do not announce an external public beta test on the same day you upload your first build; budget sufficient lead time for Apple's Beta App Review team to evaluate external builds.
- Never Rely on Timetable Guarantees: Design your shipping milestones around variable processing queues rather than assuming fixed turnaround minutes.