If you've published iOS apps, you know the Xcode IPA submission flow: Archive → Organizer → Distribute App → Upload. Each step involves various validations, and when the network is unstable, it often gets stuck during upload—and when it fails, you have to start over. But by the packaging stage, the IPA is already signed with a distribution certificate. Uploading is essentially just file transfer, so Xcode isn't strictly necessary. If you don't want to install Xcode, or if you need to submit from Windows or Linux, there are several alternatives.
Application Loader and Transporter
Apple provides a standalone macOS app called Transporter (formerly Application Loader) specifically for uploading IPA files to App Store. You don't need to open Xcode—just drag the IPA file into the app and upload. The interface is minimal, without the Archive and validation workflow. The downside is that it only runs on macOS; Windows and Linux are not supported.
Some usage notes for Transporter: after a successful upload, the build may take anywhere from a few minutes to over ten minutes to appear in App Store Connect. Sometimes the upload succeeds but the build doesn't show up for a while; usually waiting or re-uploading resolves it. You must enable two-factor authentication for your Apple developer account, and you'll need to generate an app-specific password on the Apple ID page before uploading—your regular account password won't work.
AppUploader Desktop
AppUploader works on Windows, Mac, and Linux. The upload process is straightforward: in the submission screen, select the IPA file, choose an upload channel from the four options in the upper-right corner (switch if the network environment is poor), enter your Apple ID and app-specific password, and click upload. If upload fails due to carrier restrictions or network issues, you can switch to a legacy channel or try a mobile hotspot.
AppUploader also offers a command-line version suitable for CI/CD integration. The command format is: appuploader_cli --upload-app -f Payload.ipa -u user@example.com -p xxxx-xxxx-xxxx-xxxx --type ios, specifying the IPA file, Apple ID, and app-specific password. The command-line version is more stable than the GUI version and can be embedded in automation pipelines like Jenkins or GitHub Actions. The GUI requires manual file selection and clicking upload each time, while the CLI can execute with a single command after scripting.
However, AppUploader's upload feature only supports paid developer accounts (¥688/year); free accounts cannot submit apps. If you see the message "Your account has not paid ¥688 to Apple," it means the current account is free and can only be used for development and testing.
Points to Note
Before uploading, ensure the IPA is signed with a distribution certificate—packages signed with a development certificate cannot be submitted. The IPA's Bundle ID must match the app created in App Store Connect. If the build doesn't appear in App Store Connect after a successful upload, it may be due to network latency or an issue with the app's Info.plist configuration; wait ten minutes and refresh. If it still doesn't appear, check whether the IPA includes bitcode and whether the architecture support is complete (at least arm64).
Which to Choose
If you have a Mac, Transporter is the easiest. For cross-platform IPA uploads or automation integration, AppUploader's desktop and command-line versions offer more flexibility. Neither approach requires installing Xcode.
Top comments (0)