asc-xcode-build

Build, archive, export, and upload Xcode apps to App Store Connect.

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-xcode-build-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-xcode-build
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-xcode-build
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-xcode-build-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing an iOS, macOS, tvOS, or visionOS app for App Store Connect involves error-prone xcodebuild commands, manual version and build number management, and tricky export option configuration. This Skill streamlines the entire build-to-upload pipeline using the asc xcode helpers. ## Core Features & Use Cases - Version and Build Number Management: View, edit, and bump version/build numbers, including resolving the remote-safe next build number from App Store Connect to avoid rejection for low CFBundleVersion. - Archive and Export: Run deterministic archives and exports with asc xcode archive and asc xcode export, generating ExportOptions.plist automatically with automatic or manual signing. - Upload and Publish: Upload IPA or PKG files, distribute to TestFlight groups, and publish to the App Store with optional submission. - Use Case: You need to ship a new iOS release. Bump the build number to the next remote-safe value, archive the workspace, export an IPA with automatic signing, and publish it to TestFlight—all with structured JSON output for CI pipelines. ## Quick Start Build and archive my iOS app with the asc xcode helpers, then export an IPA and upload it to App Store Connect with the next available build number.

Frequently Asked Questions about asc-xcode-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and upload an iOS app to App Store Connect from the command line?▼

Use asc xcode archive to create an .xcarchive, then asc xcode export to produce an IPA with automatic signing. Upload it with asc builds upload --app APP_ID --ipa path --wait, or publish directly with asc publish testflight or asc publish appstore.

How do I fix the CFBundleVersion too low error on App Store Connect upload?▼

Run asc xcode version edit --next-build-number --app APP_ID --platform IOS to resolve and apply the remote-safe build number from App Store Connect. Then rebuild the archive and upload again.

Can I use this with a macOS app that exports a PKG file?▼

Yes. Archive with asc xcode archive, export the PKG using xcodebuild -exportArchive with your ExportOptions.plist, then upload with asc builds upload --pkg. For PKG uploads, --version and --build-number are required since they are not auto-extracted.

Why does export fail with no profiles for bundle ID?▼

Add --xcodebuild-flag=-allowProvisioningUpdates to asc xcode export so Xcode can fetch provisioning profiles. Also verify the Apple ID is logged into Xcode and that signing is configured correctly.

When should I use raw xcodebuild instead of asc xcode commands?▼

Use raw xcodebuild only when asc xcode archive or asc xcode export do not cover a project-specific option. First try passing extra arguments through --xcodebuild-flag before falling back to raw xcodebuild.