Building and Publishing
iOS Code Signing
Store App Store Connect and signing metadata while preparing for a future macOS/Xcode build worker.
Before you start
- Apple Developer Program membership
- App Store Connect API key or signing resources
- Final bundle identifier
- Access to a Mac with Xcode for actual signing
Configure and verify
Create the app identifier
Register the exact bundle identifier in Apple Developer and App Store Connect.
Prepare App Store Connect API access
Record Issuer ID and Key ID and upload the private API key only to a trusted build system.
Prepare signing resources
Create the required distribution certificate and provisioning profile for the bundle identifier and capabilities.
Save dashboard metadata
Enter issuer, key, certificate, profile, and region fields on iOS Code Signing.
Build on macOS
Use Xcode or a future remote Mac worker to resolve Swift/Flutter dependencies, apply entitlements, sign, archive, export IPA, and upload to TestFlight.
Current outputs
Secret handling
Treat private keys and certificates as production secrets. Restrict filesystem access, avoid logs, and rotate App Store Connect keys when exposed.
Test before release
- Bundle identifier matches everywhere
- Capabilities match the profile
- Private key is restricted
- A macOS signing path is available