If your build has been sitting on Processing in App Store Connect for a full day, you are not alone, and you are probably not doing anything wrong. Processing is the quiet gap between a successful upload and a build that can actually be sent to testers or submitted to App Review. Apple does not publish a target time for it, the system status page rarely flags the slowdown, and the dashboard offers no progress signal.
Short answer
Processing is the period after a successful upload, while App Store Connect indexes the binary, extracts symbols, runs internal checks, and prepares the build for TestFlight or App Review. According to Apple's App and submission statuses reference, normal Processing finishes well inside an hour. In 2026, however, the Apple Developer Forums documented multiple backlog windows where builds sat for 10 to 24 hours, including a January incident and a March case where eight uploads from a single account stalled for more than four days. The recommended next step from Apple's own engineers is a Feedback Assistant ticket. The most common community workaround that clears a stuck slot is uploading a new build with a higher build number.
What you should know
- Processing is server-side, not local. Once Xcode or Transporter reports the upload as complete, all remaining work happens on Apple's infrastructure, where you have no visibility.
- Normal Processing is minutes, not hours. Healthy windows usually clear in 10 to 30 minutes. Anything past four hours is unusual outside an outage window.
- 24 hours is the informal alarm line. Forum patterns and Apple engineer replies converge on 24 hours as the point where filing a Feedback Assistant ticket is reasonable.
- The system status page lags reality. During the January 13 to 14, 2026 incident, the Apple Developer system status dashboard showed all green while dozens of developers reported stuck builds.
- A new build number often unsticks the slot. Re-uploading with an incremented build number tends to push the stuck artifact aside without you having to delete anything.
- Missing Compliance is a different problem. A build that processed successfully but shows Missing Compliance is waiting on the ITSAppUsesNonExemptEncryption answer, not on Processing itself.
What does Processing actually do inside App Store Connect?
Processing is the server-side phase that runs after your .ipa finishes uploading from Xcode, Transporter, Xcode Cloud, or xcrun altool. During this window, App Store Connect validates the binary, indexes symbols for crash reporting, performs internal static checks, and prepares the build entry for TestFlight or App Review. Apple's App build statuses reference lists the statuses a build can land in after Processing finishes, including Invalid Binary, Missing Compliance, Waiting for Export Compliance Review, and Ready to Submit. Processing itself is not listed there as a long-lived state, because it is meant to be transient.
The visible signals during Processing are sparse. App Store Connect shows the build in the TestFlight tab with a Processing label, occasionally an email arrives when Processing completes or fails, and Xcode Organizer mirrors the status. There is no documented progress bar, no estimated time, and no way to inspect what step is running. From the developer side, Processing either flips to a post-Processing status (good or bad) or it does not.
How long should Processing take, and when is 24 hours a real backlog?
Apple does not publish a service level for Processing. The practical baseline that developers report on the Apple Developer Forums is 10 to 30 minutes for a typical iOS build, with larger binaries (over a few hundred megabytes, dSYMs included) sometimes pushing into the one to four hour range. Anything past four hours under normal load is unusual, and 24 hours is the informal threshold at which Apple's own engineers start asking for Feedback Assistant tickets.
| Window | Typical Processing time | What it usually means |
|---|---|---|
| Under 30 minutes | Healthy | The system is operating at baseline |
| 30 minutes to 4 hours | Slow but normal | Large binary, dSYM upload, or moderate load |
| 4 to 24 hours | Backlog territory | Likely a backend incident or a stuck slot |
| Over 24 hours | Real outage for that build | File Feedback Assistant, consider reuploading with a new build number |
Two 2026 incidents anchor this picture. In January, the Apple Developer Forums thread on builds stuck in Processing for hours gathered 48 replies as developers across multiple time zones watched builds sit for 10 to 24 hours starting late on January 13. The Apple system status page showed no incident at the time. A second forum thread on TestFlight builds stuck in Processing captured another window where an Apple Developer Tools engineer eventually replied that the issue had been resolved and asked any remaining cases to file a Feedback Assistant ticket. Reports from March 2026 mentioned a four-day stall affecting eight consecutive uploads from a single developer account, which is closer to the worst case than the median.
What causes a build to sit on Processing past a day?
The honest answer is that the exact cause is rarely visible from the outside, but four patterns recur in the forums.
The first is an Apple-side backend incident. The January 2026 wave looks like a regional or queue-level processing slowdown that did not get flagged on the public status page. These windows tend to clear in 12 to 48 hours, sometimes for a single build that is stuck behind a poisoned slot.
The second is a binary or symbol issue that the system has not yet decided is fatal. Builds with corrupted dSYMs, unusual entitlements, or new SDK versions can sit in Processing while internal checks retry, and then either flip to Invalid Binary with an email or eventually clear.
The third is the export compliance interaction. A build that has finished Processing successfully but shows Missing Compliance can look identical to a stuck Processing case if you only glance at the TestFlight tab. Apple's documentation on providing export compliance information for beta builds lays out the ITSAppUsesNonExemptEncryption key path, and adding it to Info.plist removes the prompt on the next upload.
The fourth is a stuck slot on Apple's side that responds to a fresh upload. Several developers in both 2026 threads reported that incrementing the build number and pushing again caused the new build to process in minutes, after which the old stuck build either cleared or was simply ignored.
Should I upload a new build with a higher build number to unstick it?
In most cases, yes, after waiting at least a few hours. The mechanism is simple. The build number is the unique identifier inside a given marketing version, and a new value creates a fresh entry that goes through Processing independently. If the stall was a per-slot issue, the new entry usually completes in the normal 10 to 30 minutes. If the stall was a wider backlog, the new build will sit too, which itself is useful information.
A few practical notes. Increment only the build number, not the marketing version, unless you actually shipped a new release. Make sure the underlying source has a small change or recompile so the binary hash differs, since identical binaries can be deduplicated. Do not delete the stuck build before the new one finishes; if the new one fails for the same reason, you have lost both attempts at investigation. And do not chain three or four uploads in quick succession, because each one carries its own Processing cost and can amplify the queue load on the same account.
How do I file a useful Feedback Assistant ticket for a stuck Processing build?
Apple's Feedback Assistant is the documented channel that the App Store Connect engineering team monitors for these cases. A useful ticket has four parts. State the exact problem in one sentence (build x stuck in Processing for over 24 hours). Include the bundle identifier, the app's Apple ID (the numeric one from App Store Connect, not the email), the version and build number, and the upload timestamp in UTC. Attach the Xcode upload log or Transporter receipt. Reference any forum thread where others are reporting the same window, with the ticket number visible so Apple engineers can correlate cases.
For teams shipping AI-coded or no-code app builds where Processing failures are sometimes downstream of malformed entitlements or a missing Info.plist key, a pre-submission scan of the compiled .ipa can catch those issues before the upload. PTKD.com (https://ptkd.com) is one of the platforms focused on scanning compiled IPA and AAB files against OWASP MASVS controls before the artifact enters App Store Connect, which moves a class of would-be Processing failures to the local pre-flight stage.
What to watch out for
- Do not assume the system status page is authoritative. The January 2026 incident did not appear on developer.apple.com/system-status while dozens of builds were stuck.
- Do not delete the stuck build first. Re-upload with a new build number, and let the old artifact resolve in the background.
- Do not confuse Processing with Missing Compliance. If the build shows a yellow Missing Compliance label, the fix is the ITSAppUsesNonExemptEncryption key, not a Feedback Assistant ticket.
- Do not rely on email notifications alone. Several developers in both 2026 threads reported no email arrived when Processing finally completed, and the dashboard was the only signal.
- The myth that uploading from a specific region or time of day helps. Apple's processing infrastructure is global and there is no documented quiet window.
- The myth that bumping the marketing version fixes a stuck build. Only the build number identifier matters for Processing. Changing the marketing version to 1.0.1 without need can cause downstream metadata issues at App Review.
Key takeaways
- Processing is server-side preparation, not human review. Normal completion is 10 to 30 minutes, and 24 hours is the informal threshold for outside intervention.
- The two 2026 incidents in January and March show that multi-day Processing stalls are real, intermittent, and often invisible on the system status page.
- Re-uploading with a higher build number is the most common workaround that clears a stuck slot, and it does not require deleting the stuck build first.
- Missing Compliance and Processing are different states with different fixes. The ITSAppUsesNonExemptEncryption key resolves the former on your next upload.
- For teams that want pre-flight confidence on a compiled IPA before it ever enters App Store Connect, scanning against OWASP MASVS using a platform such as PTKD.com (https://ptkd.com) catches a class of malformed-binary issues that otherwise surface as a stuck Processing or Invalid Binary status hours after upload.
