-22421 (This Action could not be completed. Try Again (-22421)) usually indicates a temporary App Store Connect server outage or a stalled upload session in Xcode Organizer. The fastest workaround is to export your archive as an .ipa file and upload it using Apple’s Transporter app instead of Xcode’s built-in uploader.Why this happens
When you archive an iOS, tvOS, or macOS app in Xcode and click Distribute App, Xcode communicates with Apple’s App Store Connect backend to validate your signing assets, verify the bundle metadata, and transfer the build. The error This Action could not be completed. Try Again (-22421) is a generic failure returned during that upload handshake.
In most cases, error -22421 is caused by one of three issues:
- Transient App Store Connect server issues: Apple’s upload or authentication endpoints are temporarily degraded, overloaded, or undergoing maintenance.
- Stalled Xcode Organizer upload session: Xcode’s built-in distribution flow can fail mid-transfer due to an expired developer session token or a timeout when uploading large binaries.
- Network or proxy interference: Firewalls, corporate VPNs, or strict DNS/proxy configurations can interrupt the HTTPS upload connection between Xcode and Apple’s servers.
Because the error code itself does not pinpoint which step failed, the most reliable approach is to bypass Xcode’s direct uploader or reset the session.
How to fix it
1. Export the IPA and upload with Transporter
Rather than letting Xcode upload the build directly, export the archive as an .ipa package locally and submit it through Transporter (Apple’s standalone upload utility that replaced Application Loader). Transporter uses a separate upload pipeline and often succeeds even when Xcode Organizer throws -22421.
- Open Xcode and go to Window > Organizer.
- Select your archive in the Archives tab and click Distribute App.
- Choose App Store Connect (or Custom > App Store Connect depending on your Xcode version) and click Next.
- Select Export instead of Upload, then click Next.
- Keep your signing and distribution options as needed, click Export, and save the folder to your Desktop.
- Download and open Transporter from the Mac App Store if you do not already have it installed.
- Sign in with your Apple Developer account.
- Drag and drop the exported
.ipafile (found inside the exported folder) into the Transporter window. - Click Deliver to upload the build to App Store Connect.
Note: If you are maintaining a legacy project on an older version of Xcode prior to Xcode 11, you can use Application Loader (Xcode > Open Developer Tool > Application Loader) with the exported .ipa file in the same way.
2. Check Apple System Status and retry later
Error -22421 frequently appears during brief App Store Connect outages. Before changing project settings or regenerating certificates, verify that Apple’s services are operational:
- Visit the official Apple Developer System Status page.
- Look for App Store Connect and App Store Connect – App Processing.
- If either service shows a yellow or red indicator, wait until the outage is resolved and try uploading again.
Even when the status page shows green, regional CDN or edge-server hiccups can trigger -22421. Waiting 15 to 30 minutes and retrying the upload often resolves the issue on its own.
3. Refresh your Apple ID session in Xcode
An expired or corrupted authentication token in Xcode’s account preferences can cause App Store Connect requests to fail with -22421.
- Open Xcode > Settings (or Preferences on older macOS versions).
- Select the Accounts tab.
- Choose the Apple ID associated with your developer team.
- Click the – button at the bottom-left to remove the account, or sign out if prompted.
- Restart Xcode, return to Settings > Accounts, click +, and sign back in with your Apple ID.
- Return to Window > Organizer and retry Distribute App.
4. Check your network, VPN, and proxy settings
Xcode’s upload process requires uninterrupted connections to Apple’s upload hosts over standard HTTPS ports as well as Aspera/Signiant/HTTPS transport fallback.
- Temporarily disconnect from any VPN or corporate proxy and retry the upload.
- If you are on a restricted office or university network, test the upload on a personal hotspot or home network.
- Restart Xcode and your Mac if a previous upload hung in the background, as lingering
altoolorITunesSoftwareServiceprocesses can block subsequent attempts.
5. Upload from the command line with altool
If both Xcode Organizer and Transporter stall, you can upload your exported .ipa directly from Terminal using xcrun altool and an App Store Connect API key. This avoids Apple ID session issues entirely.
First, create an API key in App Store Connect > Users and Access > Integrations > App Store Connect API, download the .p8 file, and place it in ~/.appstoreconnect/private_keys/ (named AuthKey_YOUR_KEY_ID.p8). Then run:
xcrun altool --upload-app \
-f /path/to/YourApp.ipa \
-t ios \
--apiKey YOUR_KEY_ID \
--apiIssuer YOUR_ISSUER_ID
For Apple TV apps, change the platform flag from -t ios to -t appletvos:
xcrun altool --upload-app \
-f /path/to/YourTVApp.ipa \
-t appletvos \
--apiKey YOUR_KEY_ID \
--apiIssuer YOUR_ISSUER_ID
For macOS apps packaged as a .pkg, use -t macos.
How to prevent it
- Keep Transporter installed: Having Transporter ready on your Mac gives you an immediate fallback whenever Xcode Organizer fails to upload.
- Use App Store Connect API keys for CI/CD: Automating uploads with
xcrun altoolorxcodebuild -exportArchiveand an API key avoids interactive Apple ID token expirations. - Check System Status before debugging: Confirm App Store Connect is healthy before spending time modifying signing certificates or provisioning profiles.
- Avoid mid-upload network switches: Keep your Mac on a stable, VPN-free connection while archiving and distributing large builds.
FAQ
What does Xcode error -22421 mean?
Error -22421 (This Action could not be completed. Try Again (-22421)) is a generic App Store Connect communication error in Xcode. It typically means either Apple’s upload servers are temporarily unavailable or Xcode’s upload session failed to authenticate or complete the transfer.
Why does uploading with Transporter work when Xcode Organizer fails?
Transporter is a dedicated upload client that packages and transfers your already-signed .ipa file independently of Xcode’s Organizer workflow. It handles retries, chunked transfers, and authentication separately, which often bypasses the -22421 failure.
Can I still use Application Loader to fix error -22421?
Only if you are running Xcode 10 or earlier. Apple removed Application Loader starting with Xcode 11 and replaced it with the Transporter app, which is available for free on the Mac App Store and serves the same purpose on modern macOS and Xcode versions.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.