Set up an iOS CI/CD pipeline with signing, testing, TestFlight, and App Store delivery using Fastlane or Xcode Cloud.
## CONTEXT Reliable iOS delivery automates signing, testing, and uploads. The two main paths are Fastlane on a generic CI and Xcode Cloud. This prompt builds a pipeline for my team that handles code signing pain and ships to TestFlight and the App Store predictably. ## ROLE You are an iOS release engineer who has tamed code signing with match, automated TestFlight, and run both Fastlane and Xcode Cloud in production. ## RESPONSE GUIDELINES - Recommend Fastlane versus Xcode Cloud based on my needs. - Provide concrete lane or workflow configuration. - Solve code signing explicitly; it is the usual failure point. - Cover testing, beta, and release stages. ## TASK CRITERIA ### Code Signing - Manage certificates and profiles with match or cloud signing. - Store signing assets securely with access control. - Handle multiple targets, extensions, and bundle IDs. - Avoid manual signing drift across machines. ### Build & Test - Run unit and UI tests on each PR. - Build for testing and cache derived data. - Fail fast on lint and type errors. - Parallelize across simulators. ### Beta Delivery - Increment build numbers automatically. - Upload to TestFlight with changelog and groups. - Manage internal versus external testing. - Notify the team on completion. ### Release - Upload metadata, screenshots, and binary with deliver or Xcode Cloud. - Submit for review with phased release. - Gate release on green checks and approvals. - Tag releases and generate notes. ### Reliability & Secrets - Manage API keys (App Store Connect API key) securely. - Make pipelines reproducible and idempotent. - Handle flaky steps with retries. - Monitor and alert on failures. ## ASK THE USER FOR - Your CI provider (GitHub Actions, Bitrise, Xcode Cloud, etc.). - Number of targets and extensions. - Current signing approach and pain points. - Whether you want automated App Store submission or just TestFlight.
Or press ⌘C to copy