Introduction

If a build is "missing" in iTunes Connect, the first thing to know is that Apple now calls the service App Store Connect. In most cases the build was uploaded successfully but is still processing, attached to a different app version, or blocked by metadata, permission, or review requirements.

Start with the Right Mental Model

An uploaded archive does not become selectable immediately. Apple processes the binary first, and only then does it appear in the places where you expect to use it. Apple’s current documentation still reflects that flow: upload first, wait for processing, then choose the build for TestFlight or for the app version you want to submit.

There are two different visibility questions that often get mixed together:

• "Did Apple receive my upload?"
• "Can I select this build for TestFlight or App Review?"

A build can be present in App Store Connect but not yet available for the next step.

Verify the Build Metadata Locally

Before blaming App Store Connect, confirm that the app you archived has the right bundle identifier, marketing version, and build number. Those values determine which app record and version the upload is attached to.

/usr/libexec/PlistBuddy -c "Print :CFBundleIdentifier" MyApp/Info.plist
/usr/libexec/PlistBuddy -c "Print :CFBundleShortVersionString" MyApp/Info.plist
/usr/libexec/PlistBuddy -c "Print :CFBundleVersion" MyApp/Info.plist

You can also inspect the Xcode build settings that produced the archive:

xcodebuild -scheme MyApp -showBuildSettings | rg "PRODUCT_BUNDLE_IDENTIFIER|MARKETING_VERSION|CURRENT_PROJECT_VERSION"

If the bundle identifier points to the wrong app record, or the build number did not increase, the upload may appear somewhere you were not looking, or it may be rejected as a duplicate.

The Most Common Reasons a Build Does Not Show Up

Processing Is Not Finished

This is still the most common case. App Store Connect may show the upload in a processing state for several minutes or longer. Until that finishes, the build may not be selectable under the app version or TestFlight screen.

Version and Build Numbers Do Not Match Your Expectation

App Store Connect associates uploads using the bundle identifier and version information embedded in the app. If you created version 2.4 in App Store Connect but uploaded a binary marked 2.3, you will not see it under the 2.4 version page.

The Build Exists, but You Are Looking in the Wrong Place

For TestFlight, processed builds show up under the TestFlight tab. For App Review, you still need to attach a processed build to the version record before submitting. A build being visible in one place does not mean it is already selected in another.

Account or Contract Problems

Expired agreements, incomplete tax or banking information, or insufficient user role permissions can block distribution steps. The binary may upload, but the workflow after upload can stop.

Invalid or Incomplete Build State

If export compliance, missing symbols, unsupported entitlements, or other validation issues arise, the build may remain unusable even though the upload itself completed.

A Practical Debugging Checklist

Use a repeatable checklist instead of guessing:

11. Confirm bundle ID matches the intended app record.
22. Confirm marketing version matches the version page in App Store Connect.
33. Increment the build number for every new upload.
44. Wait for processing to finish before checking TestFlight or the version page.
55. Review App Store Connect warnings, agreements, and user permissions.
66. Check whether the build must still be selected for the version before review.

If you use CI, print the versioning values during the build so that the uploaded archive can be traced later:

echo "Bundle ID: $PRODUCT_BUNDLE_IDENTIFIER"
echo "Version: $MARKETING_VERSION"
echo "Build: $CURRENT_PROJECT_VERSION"

That small step saves a lot of time when a pipeline accidentally uploads the wrong scheme or configuration.

When to Rebuild

Do not immediately upload a new archive every time you do not see a build. Re-uploading before you confirm the root cause often creates more confusion. Rebuild only after you verify one of these conditions:

• the build number was not incremented
• the wrong bundle identifier was used
• the archive failed validation
• the upload targeted the wrong scheme or configuration

If everything is correct and the build is simply processing, waiting is the correct action.

Common Pitfalls

• Treating "uploaded" as "ready to select." Processing still has to finish.
• Checking the app version page when the build is only visible in TestFlight, or vice versa.
• Forgetting to increment CFBundleVersion for each new upload.
• Creating version X in App Store Connect and uploading build version Y.
• Ignoring account agreements and role permissions, which can block later steps without looking like upload failures.

Summary

• "iTunes Connect" issues are now App Store Connect workflow issues.
• The missing-build problem is usually caused by processing delay, mismatched metadata, or checking the wrong screen.
• Verify bundle ID, marketing version, and build number locally before troubleshooting the upload.
• A processed build may still need to be manually attached to an app version for review.
• Rebuild only when metadata or validation is wrong; otherwise, wait for processing to finish.