Build, archive, generate export options, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers. Use when creating an IPA or PKG for App Store Connect, TestFlight, or registered-device release testing.

Xcode build and export 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. Preconditions Xcode and command line tools are installed. Signing identity and provisioning profiles are available, or automatic signing is enabled. App Store Connect auth is configured when upload or build lookup is needed. Manage version and build numbers 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" and configuration "Release" for deterministic reads and writes in multi target or multi configuration projects. To avoid low build number rejects, resolve and apply the remote safe build number in one command: Version mutations validate the full change before writing and return structured output identifying the configurations and files changed. The editor follows recursive xcconfig includes and preserves unrelated project and xcconfig content. Use asc builds next build number separately when you only want to inspect the remote safe value without changing the project. Version commands read project and xcconfig settings without launching Xcode. When those settings cannot resolve the version values, the default xcodebuild settings lookup auto falls back to xcodebuild showBuildSettings and warns on stderr. Use xcodebuild settings lookup never in automation that must not launch Xcode implicitly. Compile without archiving Use asc xcode build for an ordinary simulator, device, or CI validation build. Provide exactly one project or workspace and a scheme. When derived data path is omitted, asc uses a stable cache outside the source checkout. The result bundle destination must not already exist. Xcode logs go to stderr and the structured result goes to stdout. Preferred iOS/tvOS/visionOS build flow 1. Archive with asc Use project "App.xcodeproj" instead of workspace for project only apps. 2. Export with asc By default, asc xcode export generates App Store Connect export options with automatic signing. It uses a local export destination unless wait is set, in which case it uses direct upload: Generate a plist separately when it needs review, reuse, or manual signing: For manual signing, add signing style manual and optionally team id "TEAM ID" . Existing files require overwrite . For an IPA installable on registered devices, use Xcode's current release testing method. The older ad hoc spelling is deprecated by Xcode and is not accepted by asc : Generate the release testing plist separately when it needs review or reuse: release testing always exports locally and cannot be combined with wait . An explicit export options plist cannot be combined with method , signing style , or team id . For device/profile reconciliation, isolated signing, private publication, resumability, and live verification, use the asc ad hoc distribution skill instead of assembling those stages manually. To upload directly through Xcode and wait for App Store Connect processing, omit export options and add wait : 3. Upload or publish Upload an exported IPA: Distribute to TestFlight: Publish to the App Store: macOS App Store flow Archive with the helper: If your macOS export produces a .pkg , use Xcode export with your ExportOptions.plist , then upload the package: For .pkg uploads, version and build number are required because they are not auto extracted like IPA metadata. Raw xcodebuild fallback Use raw xcodebuild only when neither asc xcode archive help nor asc xcode export help covers a project specific option. Prefer passing extra arguments through xcodebuild flag first. Troubleshooting No profiles for bundle ID during export Add xcodebuild flag= allowProvisioningUpdates to asc xcode export . Verify the Apple ID is logged into Xcode. Verify profiles with the asc signing setup skill. CFBundleVersion too low Then rebuild and upload again. Build rejected for missing macOS icon macOS requires ICNS icons with all required sizes. Fix the asset catalog, rebuild, then export/upload again. Notes Prefer asc xcode archive and asc xcode export for deterministic local artifacts. The default generated export method remains app store connect ; request method release testing explicitly for registered device installs. Use overwrite only when replacing existing local artifacts intentionally. Use wait on upload/publish paths when the next step depends on processed builds. For submission readiness, use asc submission health .

asc-xcode-build