浏览器与自动化
appstore-record-creator
App Store Connect New App creation via visible browser automation after bundle-ID registration for the API-less web form; never store cookies or auto-retry Create.
Xopoko · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Xopoko/build-swift-apps --skill appstore-record-creator技能说明
name: appstore-record-creator description: App Store Connect New App creation via visible browser automation after bundle-ID registration for the API-less web form; never store cookies or auto-retry Create.
App Store Record Creator
Opt-in local browser automation for App Store Connect app creation. The user must be signed in; the bundle ID must already exist.
Preconditions
- Playwright, Cursor browser MCP, or equivalent visible browser automation.
- User can complete login and 2FA.
- Inputs: app name (<=30 chars), registered unused bundle ID, SKU, platform(s), primary language, user access.
Guardrails
- Never export/store cookies.
- Use a visible session only.
- Pause before final Create click in standalone scripts.
- Do not retry Create automatically.
Workflow
- Preflight:
asc bundle-ids create --identifier "com.example.app" --name "My App" --platform IOS asc apps list --bundle-id "com.example.app" --output json - Open
https://appstoreconnect.apple.com/appsand confirm login. - Click the blue
+New App button, then theNew Appmenu item. It is a dropdown first, not a direct dialog. - Fill fields:
- Platform checkboxes: iOS, macOS, tvOS, visionOS; multiple allowed.
Name, max 30 chars.Primary Languagecombobox/select.Bundle IDselect: wait until async loading finishes after platform selection; choose label likeMy App - com.example.app.SKU.User Access: required radio,Limited AccessorFull Access.
- User Access radios may have span overlays; scroll the radio input into view and click the radio ref directly if accessibility click is intercepted.
- If Ember validation does not notice filled fields, clear/retype one text value slowly.
- Confirm, click Create, wait for
/apps/<APP_ID>/.... - Verify:
asc apps view --id "APP_ID" --output json --pretty asc apps list --bundle-id "com.example.app" --output json - Hand off:
Use the web availability flow only for first bootstrap; later useasc app-setup info set --app "APP_ID" --primary-locale "en-US" asc app-setup categories set --app "APP_ID" --primary GAMES asc web apps availability create --app "APP_ID" --territory "USA,GBR" --available-in-new-territories trueasc pricing availability edit.
Failure Handling
If a field/button cannot be located, stop, capture a screenshot, report the last step, and ask the user to inspect validation errors. Selectors can change; prefer role/label/text selectors over CSS.