docs: iOS multi-target signing documentation#502
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request updates iOS cloud build documentation to introduce a new multi-target provisioning profile mapping system. It replaces legacy single-profile CLI flags and environment variables with modern CAPGO_IOS_PROVISIONING_MAP support, adds new credential management flows including update and migrate commands, and documents support for multiple targets (app and extensions). Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- Document `build credentials update` with additive merge and `--overwrite-ios-provisioning-map` - Document `build credentials migrate` command in Commands section - Add `--output-upload`, `--output-retention`, `--skip-build-number-bump` to iOS options table - Replace stale `--apple-id`/`--apple-app-password` (not in CLI) - Update API key note: not required when output-upload or skip-bump set - Fix multi-target migration to use `update` instead of `save` - Clarify migrate removes legacy keys (BUILD_PROVISION_PROFILE_BASE64, APPLE_PROFILE_NAME)
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 97d9f54daa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| <Aside type="note" title="¹ App Store Connect API Key Requirements"> | ||
| - **`app_store` mode** (default): All three options are **required** — they are used to upload your build to TestFlight / App Store. | ||
| - **`app_store` mode** (default): All three API key options are **required** unless you pass `--output-upload` or `--skip-build-number-bump` (which bypass the need for API-driven submission). |
There was a problem hiding this comment.
Correct app_store API-key exception guidance
This note says --skip-build-number-bump removes the need for App Store Connect API keys in app_store mode, but that flag only controls build-number incrementing and does not switch off App Store submission; users following this guidance can omit --apple-key* credentials and hit signing/submission failures. The surrounding docs already frame “no API key” as an ad-hoc flow (see ios.mdx ad-hoc section), so this exception should be limited to scenarios that truly avoid store submission.
Useful? React with 👍 / 👎.



Summary
--ios-provisioning-profileandCAPGO_IOS_PROVISIONING_MAPbuild credentials migrate --platform iosRelated PRs
Test plan
Summary by CodeRabbit