asc-xcode-build

Build, archive, export, and upload Xcode apps to App Store Connect using asc CLI helpers.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-xcode-build-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-xcode-build
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/asc-xcode-build
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-xcode-build-omixec

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/build number management, and export options configuration. This Skill replaces that with deterministic asc xcode helper commands for archiving, exporting, and uploading. ## 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. - Archive and Export: Run asc xcode archive and asc xcode export with automatic or manual signing, generated ExportOptions.plist, and optional direct upload with --wait. - Upload and Publish: Upload IPA or PKG artifacts, distribute to TestFlight groups, or publish to the App Store with submission. - Use Case: You need to ship a new iOS release. Bump the build number with the remote-safe value, archive the workspace, export an IPA with automatic signing, and publish to TestFlight in one guided flow. ## Quick Start Use the asc-xcode-build skill to archive my iOS app, 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 archive and export an iOS app for App Store Connect from the command line?▼

Use `asc xcode archive` with your workspace or project, scheme, and Release configuration to produce an .xcarchive, then run `asc xcode export` to generate an IPA with automatic signing. Add `--wait` to upload directly through Xcode and wait for processing.

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 and upload again. This avoids rejections caused by reusing an existing build number.

Does asc xcode export support manual signing?▼

Yes. Generate an ExportOptions.plist with `asc xcode export-options generate` and add `--signing-style manual` plus optionally `--team-id`. You can then pass that plist to the export step for manual provisioning control.

How do I upload a macOS PKG to App Store Connect?▼

Export the archive with xcodebuild using your ExportOptions.plist to produce a .pkg, then run `asc builds upload --app APP_ID --pkg path --version X --build-number Y --wait`. Version and build number are required for PKG uploads since they are not auto-extracted like IPA metadata.

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

Use raw xcodebuild only when neither `asc xcode archive` nor `asc xcode export` covers a project-specific option. First try passing extra arguments through `--xcodebuild-flag`, which forwards flags to the underlying xcodebuild invocation.