issue with Xcode 27 RC uploading to App Store Connect

I'm running into the same problem. Did you figure anything out?

I haven’t yet. Just heard back from developer support who sent me to ai generated answers, which would be useful if I was using Xcode 15 instead of Xcode 27.

i put detailed comments plus logs and diagnostics in the feedback system, but I’m doubtful I’ll hear anything from that.

Update — September 13, 2026

I’ve now completed an additional diagnostic test using Xcode Cloud, which significantly narrows down the issue.

I configured Xcode Cloud to use:

• Xcode 27 Release Candidate (27A266a)
• macOS Golden Gate 27 beta 8 (26A5425a)
• The same Git repository and Xcode project
• The same application and committed Package.resolved

The workflow performed:

1. Archive – iOS
2. TestFlight Internal Testing – iOS

Both completed successfully, and the resulting build is now visible in App Store Connect/TestFlight.

This is important because my local Xcode 27 installation still hangs during the ContentDelivery / swinfo validation stage after successfully creating and packaging the archive.

So far the comparison is:

Local Xcode 27: Archive ✅ → IPA/package preparation ✅ → ContentDelivery/swinfo validation ❌ hangs

Xcode Cloud with Xcode 27: Archive ✅ → TestFlight distribution ✅ → Build appears in App Store Connect ✅

This makes an application/project problem much less likely and points increasingly toward an issue with the local Xcode 27 ContentDelivery/swinfo validation path.

I’ve also submitted the additional evidence to Apple Developer Support and updated the Feedback Assistant report. The relevant local Xcode logs and swinfo diagnostic have already been attached to the feedback report.

I’m posting this update in case anyone else experiencing the same Xcode 27 validation hang can compare their results with this Xcode Cloud test.

I had the same issue on macOS 27 with Xcode 27: app validation/upload would hang, and running xcrun swinfo directly also failed.

Deleting the old ~/.itmstransporter folder fixed it for me. After that, retry validation/upload. My folder contained old Transporter files dating back to 2018–2019.

Having the same problem. No .itmstransporter folder either.

This did work for me:

https://developer.apple.com/forums/thread/847303

Rosetta installation was missing for old commandLineTools mistakenly being used.

We've run into a similar problem with Xcode27. Validates but won't upload. Filed a bug: FB24983188

Resolved: Xcode 27 / Transporter validation hanging at “Preparing…”

UPDATE: I found the cause and was able to completely resolve the issue.

I was seeing Xcode 27 Organizer Validate App and Distribute App hang indefinitely at:

“Preparing… / Validating…”

Transporter 1.4.5 exhibited the same behavior.

The important clue came from running swinfo directly against the actual IPA.

I checked:

xcode-select --print-path

which correctly returned:

/Applications/Xcode.app/Contents/Developer

However:

xcrun --find dwarfdump-classic

returned:

/Library/Developer/CommandLineTools/usr/bin/dwarfdump-classic

I then checked the executable:

file "$(xcrun --find dwarfdump-classic)"

and found:

Mach-O 64-bit executable x86_64

Running it directly confirmed the problem:

/Library/Developer/CommandLineTools/usr/bin/dwarfdump-classic --help

returned:

zsh: bad CPU type in executable

I'm on Apple Silicon running macOS 27.0.

THE FIX

I moved the old standalone Command Line Tools installation out of the active location rather than deleting it:

sudo mv /Library/Developer/CommandLineTools
/Library/Developer/CommandLineTools-old

Then I made sure Xcode 27 was selected:

sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer

After that, xcrun could no longer find the obsolete dwarfdump-classic, which is expected because Xcode 27 no longer contains that tool.

I then reran swinfo against the same IPA.

Instead of hanging indefinitely, swinfo completed and returned to the shell. It did produce a separate bitcode-build-tool internal error, but importantly it did NOT hang.

I then archived the current branch in Xcode 27 and ran Validate App again.

It completed successfully:

“My CareCycle 1.6.0 (281) validated”

“Your app successfully passed all validation checks.”

CONCLUSION

In my case, the problem was an old standalone Command Line Tools installation containing an x86_64-only dwarfdump-classic.

Xcode 27's validation tooling was finding that executable through xcrun, and on my Apple Silicon/macOS 27 system it could not execute it.

Removing the stale Command Line Tools installation from the active path fixed the indefinite Xcode 27/Transporter validation hang.

I did not have to modify the app, signing configuration, IPA, dependencies, or App Store Connect configuration.

For anyone experiencing the same issue, these three commands should make the problem easy to confirm:

xcrun --find dwarfdump-classic

file "$(xcrun --find dwarfdump-classic)"

/Library/Developer/CommandLineTools/usr/bin/dwarfdump-classic --help

If the result is an x86_64 executable followed by:

zsh: bad CPU type in executable

you may be seeing the same issue.