submit-apple

Documents App Store submission gotchas and fixes beyond the asc CLI skills.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/allen-hsu/mobile-shipkit --skill submit-apple-allen-hsu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: submit-apple
Source: https://github.com/allen-hsu/mobile-shipkit/tree/main/skills/submit-apple
Command: npx skills add https://github.com/allen-hsu/mobile-shipkit --skill submit-apple-allen-hsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Submitting an iOS app to App Store review hits undocumented traps—expired web sessions, version string mismatches, emoji rejections, pricing timezone errors, and missing declarations—that the official asc CLI skills do not cover, causing failed submissions and wasted review cycles. ## Core Features & Use Cases - Failure Casebook: Nine field-observed traps from a real Aug 2026 submission, each with the exact asc command to diagnose and fix it, ordered along the submission flow. - Submission Sequencing: The correct five-step order for content rights, medical device declaration, submission creation, item attachment, and final submit, including which step's error output acts as the best missing-items checklist. - Human Checkpoint Markers: Explicit flags for steps requiring human action—2FA login, privacy questionnaire answers, age rating decisions, and the irreversible final submit confirmation. - Use Case: Your metadata push is rejected and the error does not explain why. The skill tells you to grep the description JSON for non-BMP emoji characters, since App Store Connect rejects emoji that Google Play allows. ## Quick Start Ask the agent to walk through the App Store submission for your app using the asc CLI, applying the submit-apple gotcha checklist at each step.

Frequently Asked Questions about submit-apple

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit an iOS app to App Store review with the asc CLI?▼

Run the steps in order: set content rights, set the medical device declaration, create a review submission, add the appStoreVersions item, then submit with --confirm. Step four's error output lists exactly what is missing, and asc review doctor performs the same check beforehand.

Why was my App Store description rejected?▼

App Store Connect rejects emoji in the description even though Google Play allows them, and the error message may not name emoji as the cause. Grep your metadata JSON files for non-BMP characters in the ranges U+1F300-1FAFF and U+2600-27BF to find the offending characters.

Why does asc web apps create keep asking for my Apple ID password?▼

Creating an app requires an Apple web session with 2FA because the public App Store Connect API cannot create apps. The session expires within hours to a day, after which every asc web command may prompt again; log in manually rather than retrying in a loop.

Why can't I attach my build to the App Store version?▼

The version string created by asc defaults to 1.0, but an Expo binary's CFBundleShortVersionString comes from app.json, often 1.0.0. Update the version string with asc versions update or pass --version when creating the app so they match.

Why does asc pricing schedule create reject today's date?▼

The start date is evaluated in Cupertino time, so 'today' in your timezone may still be tomorrow there and get rejected. Use yesterday's date instead, for example with date -v-1d +%F on macOS.

Can I upload screenshots to a version already in review?▼

No. Versions in WAITING_FOR_REVIEW, IN_REVIEW, or READY_FOR_SALE are locked and the API refuses media changes. Create the next version first, upload screenshots there, then submit that version.