Two weeks in Processing is not a long queue, it is a stuck build. TestFlight processing is an automated step that normally takes minutes, and a first build up to about a day, so a multi-week stall means something failed quietly or the build is waiting on you. The fix is rarely to keep waiting. Here is what causes it and how to unstick it, including when to escalate to Apple.
Short answer
A TestFlight build stuck on Processing for weeks is not normal, because processing usually takes minutes and a first build up to about a day. A multi-day stall almost always means the build failed silently, often with an invalid-binary email you may have missed, or it is waiting on your export compliance answer. The reliable fix is to upload a new build with an incremented build number, since a genuinely stuck build rarely recovers. Check your email and the export compliance question first, and contact Apple Developer Support if a real build stays stuck.
What you should know
- Processing is minutes, not weeks: it is an automated step, so a long stall is abnormal.
- First builds take longer: an initial build can take around a day, but not days or weeks.
- Silent failures happen: a build can fail processing and only tell you by email.
- Export compliance can block it: an unanswered encryption question leaves the build waiting.
- Re-uploading is the fix: a stuck build rarely recovers, so a new build with a higher number clears it.
Is two weeks in Processing normal?
No. Processing is the automated step that prepares your uploaded build, and it typically completes in minutes, with a first build sometimes taking up to around 24 hours. Anything beyond a day is outside the normal range, and two weeks means the build is not going to finish on its own. It is worth separating this from review: Processing is not Beta App Review, so a build stuck in Processing has not even reached the review queue yet. The cause is in the upload and preparation step, not in a reviewer's hands.
What causes a build to stick in Processing?
A few specific failures, most of which do not announce themselves clearly. The table lists them and the fix.
| Cause | Sign | Fix |
|---|---|---|
| The build failed processing silently | An invalid-binary or ITMS email, and the build vanished | Fix the issue the email names and re-upload |
| Export compliance is unanswered | The build waits for your encryption answer | Answer the export compliance question in App Store Connect |
| Interface lag after the Ready email | The email says Ready but it still shows Processing | Edit and save the build metadata to refresh the state |
| A genuine stall on Apple's side | No email and no progress past about a day | Upload a new build with a higher build number; contact support |
The most common surprise is the first row: the build failed, an email went out, and it was missed, so the build appears stuck when it has actually been rejected at the processing stage. Apple sends that email to the address on the account, so if a teammate uploaded the build or notifications are filtered, the rejection can sit unread while everyone assumes the build is still in the queue.
How do you unstick it, step by step?
Work from the cheapest check to a re-upload:
- Check your email, including spam, for an invalid-binary or ITMS message, since a silent processing failure is usually reported there.
- Answer the export compliance question in App Store Connect if the build is waiting on it.
- If you received a Ready email but it still shows Processing, edit and save the build's metadata to nudge it to Ready to Submit.
- Upload a new build with an incremented build number, which is the most reliable fix for a genuinely stuck build.
- Contact Apple Developer Support if a real, valid build stays stuck with no email and no progress, since that is the point to escalate.
When should you re-upload, wait, or escalate?
Match the action to how long it has been. Within the first hour or two, waiting is fine, since processing is still in its normal window. Past about a day with no progress and no email, stop waiting and upload a new build with a higher build number, because the stuck one is very unlikely to recover. If a fresh, valid build also stalls for a full day with no error, that is when escalating to Apple Developer Support is warranted, because the problem is more likely on Apple's side than in your build. Re-uploading is almost always faster than waiting on a stuck build to revive. Incrementing the build number matters here, because App Store Connect will not accept a duplicate build number for the same version, so bump CFBundleVersion before you upload the replacement.
What to watch out for
The first trap is treating Processing like a review queue and waiting patiently for two weeks, when processing should take minutes and a stall means a failure. The second is missing the invalid-binary email, which is the actual status of many supposedly stuck builds. Processing and review delays are on Apple's side and are separate from the security of your build, so they sit apart from a pre-submission scan; a scan such as PTKD.com (https://ptkd.com) reads the compiled IPA against OWASP MASVS for the binary's security, which is a different concern from whether the build finished processing. Fix the stall by re-uploading, not by waiting.
What to take away
- Processing takes minutes, not weeks, so a multi-week stall is a stuck or silently failed build, not a queue.
- Check your email for an invalid-binary message and answer the export compliance question first.
- Upload a new build with an incremented build number, since a genuinely stuck build rarely recovers.
- Escalate to Apple Developer Support only when a fresh, valid build also stalls, and keep the binary's security a separate check with a pre-submission scan such as PTKD.com.
