appstore-release-plannerlisted

# App Store Release Planner Use when the user asks whether an app can be submitted now or wants to prepare/submit an App Store version. ## Answer Order 1. Ready now or not. 2. Blocking issues. 3. Public API fixes vs experimental web-session/manual fixes. 4. Next exact command. Resolve `APP_ID`, version, `VERSION_ID`, and `BUILD_ID`; ensure `asc auth login` or `ASC_*`; use canonical `./metadata` when staging. ## Main Path ```bash asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table asc validate --app "APP_ID" --version "1.2.3" --platform IOS --strict --output table asc validate iap --app "APP_ID" --output table asc validate subscriptions --app "APP_ID" --output table ``` Stage without submit: ```bash asc release stage --app "APP_ID" --version "1.2.3" --build "BUILD_ID" \ --metadata-dir "./metadata/version/1.2.3" --dry-run --output table asc release stage --app "APP_ID" --version "1.2.3" --build "BUILD_ID" \ --metadata-dir "./metadata/version/1.2.3" --confirm ``` Use `--copy-metadata-from "1.2.2"` instead of `--metadata-dir` when carrying metadata forward. Submit prepared version: ```bash asc review submit --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --dry-run --output table asc review submit --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm ``` High-level upload/submit: ```bash asc publish appstore --app "APP_ID" --ipa "./App.ipa" --version "1.2.3" --submit --dry-run --output table asc publish appstore --app "APP_ID" -