Successfully uploaded iOS app builds don't appear in App Store Connect

Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received.

  1. Xcode reports successful upload (with a few warnings regarding dSYM)
  2. I'm not getting any e-mails with ITMS errors
  3. Builds don't appear at in App Store Connect in TestFlight section (not even in "Processing" or "Failed" states).

For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.

Builds are more likely to appear if you upload then late at night or early in the morning (CET time zone)

I am also seeing this issue where successfully uploaded builds do not show in TestFlight / App Store Connect. We are using Xcode 26 Beta 7 and altool with an app specific password.

We're having a somewhat similar issue where we upload two builds (two variants of our app with different bundle ids), one gets associated with the wrong app and the other disappears completely. We get an error email about the first (that gets associated with the wrong app) but nothing about the second. Also using beta 7.

We are having this same issue as combinatorial with the Release version of Xcode 26. Uploading one of our apps will attempt to associate with another app. We get an email with the error "ITMS-90055: This bundle is invalid" and it lists the bundle id of a different app than the one we uploaded.

Same issue for us. Apps uploading according to Fastlane but not appearing in TestFlight or just stuck in "Awaiting Upload"

We also have the same issue where appA uploaded with Fastlane to TestFlight seems to have been associated with appB and vice versa and we get emails from TestFlight saying build was rejected

If you are using the xcrun altool command, then you are running into a known bug. The issue occurs when you have multiple bundle IDs, the tool might pick the wrong Apple ID for your app. The workaround is to add the --apple-id <appleID> to your xcrun altool command.

For those using fastlane, there's a detailed discussion with additional workarounds here: https://github.com/fastlane/fastlane/issues/29698

Some users report that using both --apple-id and --use-old-altool flags together provides a more reliable solution than --apple-id alone.

For Fastlane, there is an open issue for this: https://github.com/fastlane/fastlane/issues/29698

And the workaround is to use an environment variable to force Fastlane to use an older altool version

export DELIVER_ALTOOL_ADDITIONAL_UPLOAD_PARAMETERS="--verbose --use-old-altool"

This worked for our app upload at least with XCode 26.0.1 17A400 and Fastlane 2.228.0.

Successfully uploaded iOS app builds don't appear in App Store Connect
 
 
Q