asc-xcode-build

Builds, archives, exports, and uploads Xcode apps for App Store Connect submission.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-xcode-build-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-xcode-build
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-xcode-build
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-xcode-build-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing an iOS, macOS, tvOS, or visionOS app for App Store Connect involves error-prone manual steps: managing version and build numbers, archiving, generating export options, exporting IPAs or PKGs, and uploading builds. This Skill standardizes that entire pipeline using the asc xcode helpers. ## Core Features & Use Cases - Version and Build Number Management: View, edit, and bump MARKETING_VERSION and CURRENT_PROJECT_VERSION, including resolving the remote-safe next build number from App Store Connect to avoid rejection. - Archive and Export: Run deterministic archives and exports with automatic or manual signing, generating ExportOptions.plist when review or reuse is needed. - Upload and Publish: Upload IPAs or PKGs, 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 with the remote-safe value, archive the Release configuration, export an IPA with automatic signing, and publish it to TestFlight in one guided flow. ## Quick Start Ask the assistant to archive the app with asc xcode archive, export an IPA, and upload it to App Store Connect for TestFlight distribution.

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?▼

Archive the app with asc xcode archive, export an IPA with asc xcode export, then upload it using asc builds upload with your app ID. Add --wait to pause until App Store Connect finishes processing the build.

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

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

Can I use manual signing instead of automatic signing for export?▼

Yes. Generate an ExportOptions.plist with asc xcode export-options generate and add --signing-style manual, optionally with --team-id. Pass that plist to the export step instead of relying on automatic signing.

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

This happens when provisioning profiles are missing or outdated. Add --xcodebuild-flag=-allowProvisioningUpdates to the export command, confirm the Apple ID is logged into Xcode, and verify profiles with the asc-signing-setup skill.

Does this workflow support macOS app PKG uploads?▼

Yes. Archive the macOS app, export with xcodebuild using your ExportOptions.plist to produce a PKG, then upload with asc builds upload. For PKG uploads, --version and --build-number are required since they are not auto-extracted.