跪拜 Guibai
← All articles
iOS · Backend

Publishing an iOS App from Windows: The 8-Step Order That Avoids Rejections and Empty Build Lists

By 开心猴爷 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

App Store submission no longer requires a Mac: Appuploader's consolidated flow runs from Windows and Linux CI, removing Xcode, Transporter, and the developer portal. The explicit verification points target the most common stalls, like empty build lists and invalid profiles, which previously forced developers into trial and error.

Summary

Submitting an iOS app to the App Store follows a strict sequence: login and team selection, a distribution certificate, a Bundle ID with capabilities, an App Store provisioning profile, an App Store Connect app record, an ipa upload, version and store metadata, then selecting that build for review. Each step has an explicit verification point, and the common failures are administrative rather than technical: using a development certificate instead of distribution, changing capabilities after generating a profile (which invalidates it), and uploading an ipa that still needs processing time before it appears in the build list.

Appuploader runs the entire chain on Windows and Linux, providing a GUI for the interactive steps and a CLI for CI pipelines. The CLI accepts an appuploader.yaml config and executes a single release command that handles certificates, profiles, app creation, upload, store info, screenshots, and submission, with resume on failure. It works on GitHub Actions, Jenkins, and GitLab CI Linux runners. The only hard requirement is a paid Apple Developer Program account; free accounts can test on a device but cannot submit.

Takeaways
— A paid Apple Developer Program membership is required to submit apps; free accounts can only test on devices.
— The submission order is: login, distribution certificate, Bundle ID with capabilities, App Store provisioning profile, app record, ipa upload, metadata, then build selection and submission.
— Using a development certificate (Apple Development) instead of a distribution certificate (Apple Distribution) gets the build rejected.
— Changing a Bundle ID's capabilities after generating a provisioning profile invalidates that profile; it must be regenerated.
— The provisioning profile for App Store submission must be of type App Store, not Development or Ad Hoc.
— After uploading an ipa, Apple processes it for a while; an empty build list means processing hasn't finished or the upload failed.
— Apps that require login must provide a demo account and password in the review information, or the submission is almost always rejected.
— Screenshots with pixel dimensions not matching any App Store device size are silently skipped; they won't appear in the listing.
— Appuploader CLI can automate the whole flow via appuploader.yaml, resume from a failed step, and run on GitHub Actions, Jenkins, and GitLab CI Linux runners.
Conclusions

The failures this flow guards against are almost entirely administrative: certificate type, profile validity, processing wait, and demo account. None involve code quality, which suggests Apple's submission gate is more about configuration discipline than about the app itself.

Appuploader's CLI support for Linux CI runners means Apple's Mac-only toolchain is no longer a hard dependency for automated builds, a shift that lowers the barrier for cross-platform teams.

Concepts & terms
Distribution certificate
An Apple-issued certificate that authorizes signing an app for distribution outside development. The Apple Distribution certificate is used for App Store releases, and its private key is exported as a .p12 file.
Provisioning profile
A file that links a certificate, a Bundle ID, and (for development) device IDs, enabling a build to be signed for a specific context. The App Store type is used for submission; changing a Bundle ID's capabilities invalidates it.
App Store Connect API key
A credential for external tools to manage app metadata and submit builds via API. The private .p8 key is shown only once at creation.
From the discussion
Featured comments
宇本尊

The process is broken down very clearly, especially the step of waiting for the build to finish processing after upload, which is easy to miss. One addition: for apps that require login, it's best to preload demo accounts with test data that can be experienced directly, and ensure they don't expire or trigger risk control during review; writing the entry path in the review notes can reduce back-and-forth caused by the inability to reproduce features.

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗