Asc Publish

**English** · [한국어](README.ko.md) · [日本語](README.ja.md) · [简体中文](README.zh-CN.md)

asc-publish — App Store Connect on autopilot

**One JSON file in, a submit-ready App Store listing out.** Bundle ID, app info, descriptions and keywords in every locale, screenshots, age rating, pricing, review notes, the build upload, the build attach — all through the App Store Connect API, with nothing but `curl`, `python3` and `openssl`.

Built as a [Claude Code](https://claude.com/claude-code) skill, but every script runs on its own.

$ python3 scripts/asc_publish.py all --app 6806932781 --meta asc-metadata.json

── app-info ──
✅ categories — PHOTO_AND_VIDEO / LIFESTYLE
✅ app info localization ko — patched
✅ app info localization en-US — created
── version ──
✅ version attributes — {'versionString': '1.0.0', 'copyright': '2026 hueeng'}
   ↳ ko: whatsNew is locked on the first version, retrying without it
✅ version localization ko — patched
✅ version localization en-US — created
── screenshots ──
✅ screenshots ko APP_IPHONE_67 — 5 uploaded, all COMPLETE
✅ screenshots ko APP_IPHONE_65 — 5 uploaded, all COMPLETE
✅ screenshots ko APP_IPAD_PRO_3GEN_129 — 5 uploaded, all COMPLETE
✅ screenshots en-US APP_IPHONE_67 — 5 uploaded, all COMPLETE
…
── age-rating ──
✅ age rating declared NONE/false for 14 fields
── price-free ──
✅ price schedule: free (USA base)
── review-details ──
✅ review details created

Why this exists

Shipping a small app means an afternoon of clicking through App Store Connect: the same description pasted into three places, thirty screenshots dragged into the right slots, the age-rating questionnaire, the export-compliance question, waiting for the build to process, attaching it. `fastlane deliver` automates this but drags in Ruby, a Fastfile and an Apple ID session. This does the same job with the **App Store Connect API key you already have** and nothing else:

• No Xcode login, no Apple ID session. The same .p8 key signs the JWT for the API and