Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill when you need to build an app from source and prepare it for App Store Connect. Prefer asc xcode archive and asc xcode export over raw xcodebuild recipes when they fit the project.
asc xcode version view
asc xcode version edit --version "1.3.0" --build-number "42"
asc xcode version bump --type build
asc xcode version bump --type patch
Use --project-dir "./MyApp" when not running from the project root. Use --project "./MyApp/App.xcodeproj" when the directory contains multiple projects. Use --target "App" for deterministic reads in multi-target projects.
To avoid low build-number rejects, resolve a remote-safe build number first:
asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS --output json
asc xcode version edit --build-number "NEXT_BUILD"
asc xcode archive \
--workspace "App.xcworkspace" \
--scheme "App" \
--configuration Release \
--clean \
--archive-path ".asc/artifacts/App.xcarchive" \
--xcodebuild-flag=-destination \
--xcodebuild-flag=generic/platform=iOS \
--output json
Use --project "App.xcodeproj" instead of --workspace for project-only apps.
asc xcode export \
--archive-path ".asc/artifacts/App.xcarchive" \
--export-options "ExportOptions.plist" \
--ipa-path ".asc/artifacts/App.ipa" \
--xcodebuild-flag=-allowProvisioningUpdates \
--output json
If ExportOptions.plist uses direct App Store Connect upload, add --wait to poll for build discovery and processing:
asc xcode export \
--archive-path ".asc/artifacts/App.xcarchive" \
--export-options "UploadExportOptions.plist" \
--ipa-path ".asc/artifacts/App.ipa" \
--wait \
--output json
Upload an exported IPA:
asc builds upload --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --wait
Distribute to TestFlight:
asc publish testflight --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --group "GROUP_ID" --wait
Publish to the App Store:
asc publish appstore --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --version "1.2.3" --wait
asc publish appstore --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --version "1.2.3" --wait --submit --confirm
Archive with the helper:
asc xcode archive \
--project "MacApp.xcodeproj" \
--scheme "MacApp" \
--configuration Release \
--clean \
--archive-path ".asc/artifacts/MacApp.xcarchive" \
--xcodebuild-flag=-destination \
--xcodebuild-flag=generic/platform=macOS \
--output json
If your macOS export produces a .pkg, use Xcode export with your ExportOptions.plist, then upload the package:
xcodebuild -exportArchive \
-archivePath ".asc/artifacts/MacApp.xcarchive" \
-exportPath ".asc/artifacts/MacAppExport" \
-exportOptionsPlist "ExportOptions.plist" \
-allowProvisioningUpdates
asc builds upload \
--app "APP_ID" \
--pkg ".asc/artifacts/MacAppExport/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.
Use raw xcodebuild only when asc xcode archive/export --help does not cover a project-specific option. Prefer passing extra arguments through --xcodebuild-flag first.
xcodebuild -showBuildSettings -scheme "App"
--xcodebuild-flag=-allowProvisioningUpdates to asc xcode export.asc-signing-setup skill.asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS
asc xcode version edit --build-number "NEXT_BUILD"
Then rebuild and upload again.
macOS requires ICNS icons with all required sizes. Fix the asset catalog, rebuild, then export/upload again.
asc xcode archive and asc xcode export for deterministic local artifacts.--overwrite only when replacing existing local artifacts intentionally.--wait on upload/publish paths when the next step depends on processed builds.asc-submission-health.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Authoritative App Intents best practices from Apple: execution model, entities, queries, parameters, enums, dependencies, and donations.
The English summary is being prepared. Showing the original description.
New App Intents APIs and behaviors for iOS 27 and macOS 27: SnippetIntent, LongRunningIntent, execution modes, and interactive snippets.
The English summary is being prepared. Showing the original description.
Apple Human Interface Guidelines as structured design values — system colors (incl. increased-contrast variants), the full Dynamic Type ramp, Liquid Glass rules and budgets, layout and hit-target metrics, SF Symbols, and HIG-to-SwiftUI component mappings. Use when styling or reviewing any Apple-platform UI: picking a color, size, spacing, corner radius, or hit target; writing .glassEffect / material code; choosing an SF Symbol; or answering 'what does the HIG say about X'.
The English summary is being prepared. Showing the original description.
Run an offline ASO audit on canonical App Store metadata under `./Store` and surface keyword gaps using Astro MCP. Use after pulling metadata with `asc metadata pull`.
The English summary is being prepared. Showing the original description.
Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
The English summary is being prepared. Showing the original description.
Guidance for using asc 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.
The English summary is being prepared. Showing the original description.