Merge pull request #79 from rorkai/codex/sync-5.3.0-xcode-pkg

docs(skills): use asc export for macOS packages
This commit is contained in:
Rudrank Riyam
2026-09-14 15:00:27 +05:30
committed by GitHub
+8 -8
View File
@@ -172,24 +172,24 @@ asc xcode archive \
--output json
```
If your macOS export produces a `.pkg`, use Xcode export with your `ExportOptions.plist`, then upload the package:
If your macOS export produces a `.pkg`, export it with the helper, then upload the package:
```bash
xcodebuild -exportArchive \
-archivePath ".asc/artifacts/MacApp.xcarchive" \
-exportPath ".asc/artifacts/MacAppExport" \
-exportOptionsPlist "ExportOptions.plist" \
-allowProvisioningUpdates
asc xcode export \
--archive-path ".asc/artifacts/MacApp.xcarchive" \
--pkg-path ".asc/artifacts/MacApp.pkg" \
--xcodebuild-flag=-allowProvisioningUpdates \
--output json
asc builds upload \
--app "APP_ID" \
--pkg ".asc/artifacts/MacAppExport/MacApp.pkg" \
--pkg ".asc/artifacts/MacApp.pkg" \
--version "1.0.0" \
--build-number "123" \
--wait
```
For `.pkg` uploads, `--version` and `--build-number` are required because they are not auto-extracted like IPA metadata.
For `.pkg` uploads, `--version` and `--build-number` are required because they are not auto-extracted like IPA metadata. Add `--export-options "ExportOptions.plist"` when the project needs a custom export configuration.
## Raw xcodebuild fallback