iOS releases for a ride-hailing app depend on one person clicking through Xcode. How would you build a pipeline that runs from signing to TestFlight upload on CI?
Keep the certificates and provisioning profiles on CI only, through fastlane match or a base64 secret, and authenticate to App Store Connect with a key instead of an Apple ID. Run the tests on every pull request, and once a tag lands on main, archive in a temporary keychain and upload to the TestFlight internal group automatically, leaving external distribution to a human approval.
Build and distributionShort answerAdvanced
If you designed an iOS CI/CD pipeline from scratch, what steps would the pipeline that…
#ci-cd #testflight #automation
Build and distributionShort answerBasics
A hiring manager looks up from your resume. "How did you run beta testing and CI/CD?"…
#ci-cd #testflight
Build and distributionShort answerExpert
Over a hundred iOS engineers work on one app here. Hundreds of pull requests land a day…
#ci-cd
Build and distributionShort answerBasics
How do Development, Ad Hoc, Enterprise (In-House), and App Store distribution, TestFlight…
#testflight