Build processing is Apple's check and preparation of an uploaded archive, and while it runs the build sits in Processing and can't be distributed in TestFlight. If Processing lasts more than 24 hours, Apple suggests filing a Feedback Assistant report (App Store Connect Help, checked October 16, 2026).
What happens after you upload
You upload a build from Xcode with Distribute App, with the Transporter app, with altool or from Xcode Cloud. App Store Connect then processes it, and only after that does it show up in the list. You get an email for each outcome, Processing, Failed and Complete.
A build has two layers of status. The upload status in the Build Uploads table tells you how delivery went. The build status on the TestFlight tab tells you what you can do next, hand it to your team, send it for review, or answer a question first.
Where the statuses live in App Store Connect
Go to Apps › your app › TestFlight and pick the platform on the left. The Build Uploads table shows delivery, and the All Statuses filter at the top right can narrow it to, say, Failed only. Click a status to see its errors and warnings.
For the App Store, you pick the build inside the version. Go to Apps › your app › version › Build › +, select the build in the Add Build dialog, press Done and then Save at the top right. A version takes exactly one build, and you can swap it as often as you like until the version is submitted.
Apple's statuses and deadlines
| Status | What it means |
|---|---|
| Processing | still being processed, over 24 hours is a reason to contact Apple |
| Failed | processing ended with an error, the same build number can be uploaded again |
| Complete | processed successfully and ready for testing |
| Invalid Binary | didn't meet the upload requirements, a new build is needed |
| Missing Compliance | no answer to the encryption question yet |
| Ready to Submit | can go to your team or be sent for review |
| Not Available for Testing | the provisioning profile lacks an application identifier |
| Expired | 90 days have passed, closed for TestFlight |
| Ready to Test, Testing | green statuses, the build can be tested or already is |
| Requirements for new builds | Xcode 26 and the 26 SDKs since April 28, 2026, a target of iOS 13 or later since September 9, 2026 |
Per App Store Connect Help (View builds and metadata, App build statuses, Choose a build to submit) and Apple's upload requirements, checked October 16, 2026. Apple's help lists 12 build statuses, the table shows the main ones.
Why your build isn't in the list. What to check
- Look at Build Uploads. If it says Processing, wait for the email. If it says Failed, open the status, fix the errors and upload again, keeping the same number if you like.
- Check the status on the TestFlight tab. Missing Compliance clears once you answer the encryption question, see the export compliance page.
- If a tester sees No builds available, make sure the build was added to their group. In an external group it opens only after TestFlight review, and Waiting for Review or In Beta Review mean that review is still under way.
- Check the build's age. After 90 days it becomes Expired, and testing needs a new one.
- If the build is missing from the Add Build dialog, compare version numbers. The dialog shows only builds for that version, and if the previous version is already Ready for Distribution, only those uploaded after it went live.
- If Processing lasts more than 24 hours, file a Feedback Assistant report under Developer Tools & Resources › TestFlight with the version and build numbers, the upload date and time, and logs.
Version number and build number
The version number (CFBundleShortVersionString, the Version field in Xcode) is what customers see, three integers separated by periods, like 1.4.0. The build number (CFBundleVersion, the Build field) is for machines, one to three integers separated by periods, with missing ones read as zeros, so 10 means 10.0.0. Both fields take only digits and periods.
Within one version, every upload needs a new build number. There is one exception, after a Failed upload the number can be reused.
Common mistakes
- Re-uploading while Processing runs. The email will come on its own, and a second upload with a new number just adds clutter to the list.
- Building with an old Xcode. Since April 28, 2026 App Store Connect accepts builds made with Xcode 26 and the iOS 26 SDK, and since September 9, 2026 the target must be iOS 13 or later.
- A provisioning profile without an application identifier. The build then shows Not Available for Testing, and only a new build with the right profile fixes it.
- Reading Ready to Submit as submitted. The status means the build can go to your team or be sent for review, it hasn't gone anywhere yet.
Appto takes care of the build and the final checklist in App Store Connect, then sends the version to Apple from your account or shows you what to press. More on the App Store Connect page.
Questions
How long does build processing take?
Apple gives no duration and only says that Processing for more than 24 hours may mean a problem. You get an email when processing finishes.
Why does TestFlight say No builds available?
Apple's statuses point to several causes. The build is still Processing, waits for the encryption answer, isn't in the tester's group, waits for TestFlight review for an external group, or is older than 90 days.
Why is my build greyed out or missing when I add it to a version?
The Add Build dialog lists only builds for that version, uploaded after the previous version went live. A build in Missing Compliance can be selected, but you must answer the encryption question before submitting.
Can I upload a build with the same build number?
Only if the earlier upload with that number ended as Failed. Otherwise every build number within a version has to be new.
What does Invalid Binary mean?
Apple received the build, but it didn't meet the upload requirements. Fix the errors App Store Connect reports and upload the build again.
Build your own app in Appto
Appto checks the niche on fresh App Store data, designs the screens, writes the code, builds the App Store page and submits to Apple from your account or shows you what to press in App Store Connect. Runs on your own Claude Code or Codex.
Download for Mac