The episode explains why iOS CI/CD is far more complex than web deployment, focusing on Apple’s April 28 2026 mandate to use Xcode 26 and the iOS 26 SDK, the shift to Apple‑Silicon macOS runners, and the deprecation of legacy services like Microsoft App Center. Listeners learn how authentication now requires a .p8 App Store Connect API key, how signing certificates and provisioning profiles must be managed securely, and why the hardware licensing model drives higher costs on platforms such as GitHub Actions and GitLab.
The discussion then compares dedicated iOS‑focused services—Xcode Cloud, Bitrise, Codemagic, and self‑hosted AppCircle—and introduces Capco Build for Capacitor apps, which lets a Linux runner offload the macOS build step. It also covers remote iOS simulators from Argent Cloud and practical migration pitfalls like exporting .p12 keys, build‑number continuity, and export‑compliance flags.
Topics:
- Apple’s Xcode 26 requirement and its impact on CI pipelines
- Using .p8 API keys to replace fragile Apple ID logins
- Choosing between Xcode Cloud, Bitrise, Codemagic, and AppCircle
- Capco Build for hybrid Capacitor apps to avoid macOS runners
- Migration checklist: certificates, build numbers, and encryption flags
Full article
https://capgo.app/blog/comparing-ci-cd-platforms-for-ios-apps/