Introduction

When Xcode appears stuck at "Your application is being uploaded," the archive is often already valid and the problem is in the upload pipeline rather than in compilation or code signing itself. The most useful troubleshooting pattern is to separate archive export from upload, then rule out account, network, and Xcode-session issues one layer at a time.

Separate Export from Upload

The first useful test is to export the archive independently. If export succeeds, the archive itself is probably fine.

1xcodebuild -exportArchive \
2  -archivePath build/MyApp.xcarchive \
3  -exportOptionsPlist ExportOptions.plist \
4  -exportPath build/export

If this works but Organizer hangs during upload, the problem is more likely in transport, authentication, or Xcode state than in the build artifact.

Check App Store Connect Basics

Upload stalls are sometimes caused by mismatches that the UI surfaces poorly. Verify:

• the bundle identifier matches the App Store Connect app record
• the version and build number are valid
• account agreements are current
• the Apple account used in Xcode has the right role
• certificates and provisioning profiles are still valid

Even when the archive compiles and signs correctly, these account-level constraints can still block the upload path later.

Rule Out Network and Proxy Issues

Uploads are sensitive to unstable connections, VPNs, proxies, and corporate packet inspection. A couple of quick checks help determine whether the machine has an obvious transport problem:

networkQuality

ping appstoreconnect.apple.com

These commands do not prove the whole upload path is healthy, but they can quickly reveal whether the machine itself is struggling.

If you are on a VPN or restricted network, retry on a cleaner connection before changing project settings.

Try Transporter or a Fresh Xcode Session

If Organizer keeps hanging, a practical workaround is to export the build and upload it with Apple's Transporter app. This helps distinguish "the archive is bad" from "Xcode's upload session is wedged."

It is also worth trying:

• quit and reopen Xcode
• sign out and back in to the Apple account inside Xcode
• restart the Mac if upload processes appear stuck

These are not elegant fixes, but stale session state is a real cause of repeated upload hangs.

Clean Local Xcode State Only When Needed

If the issue appears tied to local Xcode state rather than the archive, clearing derived data can help:

rm -rf ~/Library/Developer/Xcode/DerivedData

This should not be the first answer to every upload problem, but it is reasonable when Organizer behaves inconsistently across retries.

Consider Apple-Side Service Issues

Sometimes the archive, account, and local machine are all fine and the delay is on Apple's side. If several retries behave the same way and the usual checks look clean, consider a temporary App Store Connect or transport outage before you start changing build settings that were already working.

At that point, retrying later is often more productive than introducing new variables into the project.

Common Pitfalls

Assuming every upload stall must be a code-signing failure can send debugging down the wrong path when the issue is actually the network or the upload session.

Retrying the same Organizer flow repeatedly without first verifying that the archive exports cleanly usually wastes time.

Changing project settings during a temporary Apple-side service issue often creates more confusion than the original problem.

Ignoring VPN, proxy, or restrictive corporate-network conditions can hide the real cause of a valid archive failing to upload.

Treating Xcode Organizer and Transporter as equivalent retry paths misses a useful way to isolate the problem.

Summary

• A stuck Xcode upload often means the archive exists and the transport step is failing.
• Export the archive separately to isolate build problems from upload problems.
• Recheck bundle id, version, account state, and signing basics.
• Rule out VPN, proxy, or unstable network issues early.
• If Organizer keeps hanging, try uploading the exported build with Transporter.