You're automating the archive and the App Store upload on a CI server. How would you handle certificates, provisioning profiles, and App Store Connect authentication there safely?
Use fastlane match (certificates and profiles in an encrypted Git or S3 store, installed into a temporary keychain on CI) or Xcode Cloud managed signing, and authenticate uploads with an App Store Connect API key (.p8) so 2FA never comes up. Secrets live in the CI secret store and signing is pinned to manual.
Build and distributionShort answerIntro
How do the bundle ID, the certificate, and entitlements connect to a provisioning profile?
#code-signing
Build and distributionMultiple choiceBasics
Archiving on your Mac fails with Provisioning profile "AppStore Profile" doesn't include…
#code-signing
Build and distributionMultiple choiceBasics
What do you need to sign a build for App Store submission? Select all that apply.
#code-signing
Build and distributionShort answerAdvanced
This one comes up onsite. "If you had to pick between a monorepo and several small…
#ci