القائمة
Build, archive, and export iOS/macOS apps with xcodebuild before uploading to App Store Connect. Use when you need to create an IPA or PKG for upload.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
Guidance for using the App Store Connect CLI in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
Sync and validate App Store metadata and localizations with asc, including Fastlane format migration. Use when updating metadata or translations.
End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.
Preflight App Store submissions, submit builds, and monitor review status with asc. Use when shipping or troubleshooting review submissions.
| name | asc-xcode-build |
| description | Build, archive, and export iOS/macOS apps with xcodebuild before uploading to App Store Connect. Use when you need to create an IPA or PKG for upload. |
Use this skill when you need to build an app from source and prepare it for upload to App Store Connect.
xcodebuild clean archive \
-scheme "YourScheme" \
-configuration Release \
-archivePath /tmp/YourApp.xcarchive \
-destination "generic/platform=iOS"
xcodebuild -exportArchive \
-archivePath /tmp/YourApp.xcarchive \
-exportPath /tmp/YourAppExport \
-exportOptionsPlist ExportOptions.plist \
-allowProvisioningUpdates
A minimal ExportOptions.plist for App Store distribution:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store-connect</string>
<key>teamID</key>
<string>YOUR_TEAM_ID</string>
</dict>
</plist>
asc builds upload --app "APP_ID" --ipa "/tmp/YourAppExport/YourApp.ipa"
xcodebuild archive \
-scheme "YourMacScheme" \
-configuration Release \
-archivePath /tmp/YourMacApp.xcarchive \
-destination "generic/platform=macOS"
xcodebuild -exportArchive \
-archivePath /tmp/YourMacApp.xcarchive \
-exportPath /tmp/YourMacAppExport \
-exportOptionsPlist ExportOptions.plist \
-allowProvisioningUpdates
macOS apps export as .pkg files. Upload with asc:
asc builds upload \
--app "APP_ID" \
--pkg "/tmp/YourMacAppExport/YourApp.pkg" \
--version "1.0.0" \
--build-number "123"
Notes:
--pkg automatically sets platform to MAC_OS..pkg uploads, --version and --build-number are required (they are not auto-extracted like IPA uploads).--wait if you want to wait for build processing to complete.Each upload requires a unique build number higher than previously uploaded builds.
In Xcode project settings:
CURRENT_PROJECT_VERSION - build number (e.g., "316")MARKETING_VERSION - version string (e.g., "2.2.0")Check existing builds:
asc builds list --app "APP_ID" --platform IOS --limit 5
-allowProvisioningUpdates flagmacOS requires ICNS format icons with all sizes:
The build number must be higher than any previously uploaded build. Increment CURRENT_PROJECT_VERSION and rebuild.
xcodebuild -showBuildSettings to verify configurationasc-submission-health skill