asc-app-create-ui
Automate App Store Connect app creation by driving the web UI form with browser automation.
- Requires a pre-registered bundle ID in the Apple Developer portal and user sign-in to App Store Connect; handles multi-platform selection (iOS, macOS, tvOS, visionOS) and all required fields including the tricky User Access radio buttons
- Includes detailed workarounds for known UI quirks: dropdown menu navigation for "New App", asynchronous Bundle ID dropdown loading, and span-overlay interception on radio buttons
- Provides preflight checks via public API to verify bundle ID registration and confirm no existing app record, plus post-creation verification and handoff to setup workflows
- Enforces safety guardrails: visible browser sessions only, no cookie export, confirmation pause before final Create click, and no automatic retries on failure
asc app create (UI automation)
Use this skill to create a new App Store Connect app by driving the web UI. This is opt-in, local-only automation that requires the user to be signed in.
Preconditions
- A browser automation tool is available (Playwright, Cursor browser MCP, or equivalent).
- User is signed in to App Store Connect (or can complete login + 2FA).
- The bundle ID must already be registered in the Apple Developer portal.
- Required inputs are known:
- app name (max 30 characters)
- bundle ID (must exist and be unused by another app)
- SKU
- platform (iOS, macOS, tvOS, visionOS)
- primary language
- user access (Full Access or Limited Access)
Safety Guardrails
- Never export or store cookies.
More from rudrankriyam/app-store-connect-cli-skills
asc-cli-usage
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.
2.3Kasc-xcode-build
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.
2.3Kasc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
2.2Kasc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
2.2Kasc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
2.2Kasc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
2.1K