# App Store Connect build statuses: Processing, Missing Compliance and more

> What each build status in App Store Connect and TestFlight means, what to do about it, when Processing is taking too long, and the emails Apple sends.

- Canonical page: https://obelisk.club/blog/app-store-connect-build-processing-states
- Author: Peter Zhang
- Published: 2026-11-01
- Tags: app-store-connect, testflight, builds, checklist, indie

After you upload a build, App Store Connect shows it in two places. **Build Uploads** on the TestFlight tab tracks the upload itself: **Processing**, **Failed** or **Complete**. Once processing is done, the build gets a **build status** in the builds table, such as **Missing Compliance**, **Ready to Submit**, **Testing** or **Expired**. Apple says a build that stays in Processing "for more than 24 hours" may have a problem, and it emails you when processing finishes or fails. Below is every status Apple lists, what it means and what to do.

## Two kinds of status

- **Upload status** (Build Uploads section): where the delivery is. Apple: "The upload status provides detailed insights into delivery progress, including warnings, errors, and other information."
- **Build status** (builds table): what the build can be used for. Apple: "The status applies to the build only, not the entire app."

The build status has a colour. Apple: red "means that you need to perform some action or the build is expired", yellow "means that some process is ongoing, controlled either by you or by Apple", and green "means the build is being tested in TestFlight."

Your app's review status on the App Store (Waiting for Review, In Review and so on) is a separate list on the version page, not covered here.

## Upload statuses: Processing, Failed, Complete

You find these on the TestFlight tab: pick the platform, expand **Build Uploads** and read the Status column. The **All Statuses** menu filters the list.

| Status | Apple's description | What to do |
|---|---|---|
| Processing | "Your build upload is still being processed." | Wait for the email. If it is still Processing after 24 hours, contact Apple (see below). |
| Failed | The upload "has finished processing, but encountered an issue." | Select it to read the errors, fix all of them, upload again. |
| Complete | "Your build upload has processed successfully and is now ready for testing." | Check for a warning badge, then test or submit. |

Notes from Apple's page:

- **Failed builds free their number.** "If the build upload fails, you can reuse the same build number for your next upload."
- **Complete can still carry warnings.** "Even if the status is Complete, there may still be warnings or other details you should review and address before your next upload."
- **First upload.** "The first time you upload a build, a beta version of the app is created in your account. However, the build needs to be processed in Apple's system before it appears in App Store Connect."

To decode an error code from a failed upload or an Apple email, paste it into the [ITMS error lookup](/tools/itms-error-lookup).

## How long Processing takes

Apple doesn't give a typical processing time. The only number it publishes is the point where you should ask for help: "If you upload a build and it remains in the Processing state for more than 24 hours, there may be an issue. To resolve the issue, submit a Feedback Assistant ticket or contact us."

For a Feedback Assistant ticket, Apple names the area (**Developer Tools & Resources > TestFlight**) and asks you to include "version and build numbers, upload date and time, and relevant logs."

## Build statuses after processing

These come from Apple's App build statuses reference. Two of them, Invalid Binary and Rejected, are "Not visible in TestFlight" for internal and external testing.

| Status | Apple's description | What to do |
|---|---|---|
| Invalid Binary | "Apple received your build, but it didn't meet all the upload requirements." | Fix the issue and upload again. Look up the error in the [ITMS error lookup](/tools/itms-error-lookup). |
| Missing Compliance | "Your build is missing export compliance documentation. Action is needed." | Answer the encryption questions (see below). |
| Waiting for Export Compliance Review | "Documentation for export compliance has been submitted and is in review." | Nothing: "No action is needed on your end." |
| In Compliance Review | "Documentation for export compliance is in review." | Nothing. |
| Ready to Submit | The build "can be distributed to internal testers, or can be submitted to TestFlight App Review for external testing or to App Review for distribution to customers." | Add internal testers, add it to an external group, or attach it to a version. |
| Waiting for Review | "Your build has been submitted to TestFlight App Review." | Wait; it needs approval before external testing. |
| In Beta Review | "Your build is currently being reviewed by TestFlight App Review." | Wait. |
| Not Available for Testing | "the provisioning profile is missing an application identifier." | Upload a new build that includes the application identifier. |
| Expired | The build "has passed its 90-day availability window." | Upload a new build to keep testing. |
| Rejected | "rejected by TestFlight App Review and can no longer be used in TestFlight." | Fix the problem and upload a new build. |
| Ready to Test | Testers can use it, "but you haven't added any testers yet." | Add a group or testers. You may have chosen to notify testers yourself after approval. |
| Testing | "Your build is being tested by at least one group or tester." | Keep testing or submit the version for App Review. |

Apple notes for Testing that "Testers that have received an invite to test will still be able to test your build even after it's available for customers." You can end that early with **Expire Build** on the build page; after that "The build no longer allows internal and external testers to install it."

For testers, groups and TestFlight App Review, see the [TestFlight checklist](/blog/testflight-checklist).

## Missing Compliance

This is the status most people meet first. Every build has to say whether it uses encryption. To clear it:

1. On the TestFlight tab, open the build that is missing compliance information.
2. Click **Manage** to answer the questions, or **Choose File** to upload previously approved documentation.
3. If documentation is required, Apple sends you to the App Encryption page and gives you a key value to put in Xcode.

To stop the question coming back with every upload, Apple says you can declare encryption use in the app's Info.plist in Xcode, which "eliminates the need to answer encryption questions with each app submission." The [App encryption and export compliance](/tools/app-encryption-export-compliance) tool walks through the questions and gives you the Info.plist entry.

The same check applies when you submit to the App Store. Apple: "If you select a build with the Missing Compliance status, you must answer the export compliance questions before submitting for review."

## The emails Apple sends

- **Upload progress.** "In addition to status updates in App Store Connect, you'll also receive email notifications when your build is Processing, Failed, or Complete."
- **Processing finished.** The upload page repeats it: "You'll receive an email when this process is complete."
- **Large downloads.** If any device variant is over "the 200 MB over-the-air download limit", App Store Connect shows a yellow warning icon and "Apple also sends you an email with this information."
- **App status changes.** The **App Status Reports** user notification "Provides email alerts when an app changes state". Apple lists it for the Account Holder, Admin, App Manager, Developer and Marketing roles.

Apple's help pages don't say who on the team gets the upload emails or show their exact wording.

## A build doesn't show up when choosing one for review

When you add a build to an app version, Apple says: "If an earlier version of your app is Ready for Distribution, the list only includes builds you have uploaded since that version was released on the App Store." You can attach only one build to each version, and you can change it as often as you like until you submit. Apple also notes that "Some builds may no longer appear after the app is released."

## FAQ

### How long does build processing take?

Apple doesn't publish a usual time. It says that more than 24 hours in Processing may mean a problem, and that you should then file a Feedback Assistant ticket or contact Apple.

### What is the difference between Failed and Invalid Binary?

Failed is the upload status in Build Uploads, with the errors listed when you select it. Invalid Binary is the build status: Apple received the build but it "didn't meet all the upload requirements". In both cases you fix the issue and upload again.

### Can I reuse the build number after a failed upload?

Yes. Apple: "If the build upload fails, you can reuse the same build number for your next upload."

### Why does my build say Ready to Test but nobody has it?

Ready to Test means approved but with no testers added yet. Add a group or individual testers; Apple notes you may have chosen to notify testers yourself after approval.

### Does Missing Compliance block App Store submission too?

Yes. You must answer the export compliance questions before submitting a build with that status for review.

## Sources

All read on 1 November 2026.

- [App build statuses](https://developer.apple.com/help/app-store-connect/reference/app-uploads/app-build-statuses), App Store Connect Help
- [View builds and metadata](https://developer.apple.com/help/app-store-connect/manage-builds/view-builds-and-metadata), App Store Connect Help
- [Upload builds](https://developer.apple.com/help/app-store-connect/manage-builds/upload-builds), App Store Connect Help
- [Choose a build to submit](https://developer.apple.com/help/app-store-connect/manage-builds/choose-a-build-to-submit), App Store Connect Help
- [Provide export compliance information for beta builds](https://developer.apple.com/help/app-store-connect/test-a-beta-version/provide-export-compliance-information-for-beta-builds), App Store Connect Help
- [View build status and metrics](https://developer.apple.com/help/app-store-connect/test-a-beta-version/view-build-status-and-metrics), App Store Connect Help
- [Stop testing a build](https://developer.apple.com/help/app-store-connect/test-a-beta-version/stop-testing-a-build), App Store Connect Help
- [User notifications](https://developer.apple.com/help/app-store-connect/reference/account-management/user-notifications), App Store Connect Help

*Apple's statuses and wording change; check the pages above for current details.*