agentleFS
moasqmoasq/ios-dev-agent/.agents/skills/asc-submission-health/SKILL.md

asc-submission-health

Skill4 starsChanged 6 months agoMITView on GitHub

Use when preflighting an App Store submission, running asc validate, checking review readiness, submitting a build, monitoring review status, or diagnosing submission blockers with asc.

9 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use asc-apple-ads, asc-in-app-events and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rudrankriyamSkill

    asc-apple-ads

    Use when managing Apple Ads with asc, including OAuth profiles, ad-account discovery, Platform API v1 campaigns and targeting, reports, assets, recommendations, guarded mutations, raw requests, and migrating existing v5 scripts.

    Also in 4 projects that use this

  • rorkaiSkill

    asc-in-app-events

    Create and localize App Store in-app events, upload event media, and submit or recover event review submissions with asc. Use when managing in-app events, event card or details page assets, or event-specific submission errors.

    Also in 4 projects that use this

  • eugenepyvovarovSkill

    swift-concurrency-expert

    Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

    Also in 3 projects that use this

  • kingsidharthSkill

    swiftui-pro

    Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

    Also in 4 projects that use this

  • jamesrochabrunSkill

    swift-concurrency

    Guide for building, auditing, and refactoring Swift code using modern concurrency patterns (Swift 6+). This skill should be used when working with async/await, Tasks, actors, MainActor, Sendable types, isolation domains, or when migrating legacy callback/Combine code to structured concurrency. Covers Approachable Concurrency settings, isolated parameters, and common pitfalls.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 8 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to reduce review submission failures and monitor review state.

    line 8
  2. Distinctive:

    Use strict mode when warnings should fail automation:

    line 35
  3. Distinctive:

    If you already have the exact version ID:

    line 41
  4. Distinctive:

    If the build uses non-exempt encryption:

    line 49
  5. Distinctive:

    If the app truly uses only exempt transport encryption, prefer updating the local plist and rebuilding:

    line 66
  6. Distinctive:

    Use JSON when you need exact diagnostics:

    line 123
  7. Very specific:

    Use asc review submit for explicit App Store review submission:

    line 150
  8. Very specific:

    Use --version-id "VERSION_ID" when you have already resolved the version.

    line 157
  9. Very specific:

    Add --wait when the command should wait for build processing.

    line 166
  10. Distinctive:

    Use the lower-level review-submission API when the submission needs multiple review items, such as Game Center component versions:

    line 170
  11. Distinctive:

    Use the exact app-info ID:

    line 218
  12. Distinctive:

    Do not use legacy submit-preflight or submit-create shortcuts.

    line 226
  13. Very specific:

    Use asc validate for readiness.

    line 227
  14. Very specific:

    Use asc review submit for prepared-version submission.

    line 228
  15. Very specific:

    Use asc publish appstore --submit --confirm for high-level upload plus submission.

    line 229
  16. Very specific:

    Use --output table for human status and JSON for automation.

    line 231

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

asc submission health

Use this skill to reduce review submission failures and monitor review state. The current readiness command is asc validate; legacy submit-preflight and submit-create shortcuts must not be used.

Preconditions

  • Auth configured and app/version/build IDs resolved.
  • Build processing completed or the command uses a high-level flow with --wait.
  • Metadata, app info, screenshots, review details, content rights, encryption, pricing, and availability are expected to be complete.

Pre-submission checklist

1. Verify build status

asc builds info --build-id "BUILD_ID"

Check:

  • processingState is VALID.
  • encryption fields are understood before submission.

2. Run canonical readiness validation

asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table

Use strict mode when warnings should fail automation:

asc validate --app "APP_ID" --version "1.2.3" --platform IOS --strict --output table

If you already have the exact version ID:

asc validate --app "APP_ID" --version-id "VERSION_ID" --platform IOS --output table

3. Encryption compliance

If the build uses non-exempt encryption:

asc encryption declarations list --app "APP_ID"

asc encryption declarations create \
  --app "APP_ID" \
  --app-description "Uses standard HTTPS/TLS" \
  --contains-proprietary-cryptography=false \
  --contains-third-party-cryptography=true \
  --available-on-french-store=true

asc encryption declarations assign-builds \
  --id "DECLARATION_ID" \
  --build "BUILD_ID"

If the app truly uses only exempt transport encryption, prefer updating the local plist and rebuilding:

asc encryption declarations exempt-declare --plist "./Info.plist"

4. Content rights declaration

asc apps content-rights view --app "APP_ID"
asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false

5. Version metadata and localizations

asc versions view --version-id "VERSION_ID" --include-build --include-submission
asc localizations list --version "VERSION_ID" --output table

For canonical metadata repair:

asc metadata pull --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata"
asc metadata validate --dir "./metadata" --output table
asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --dry-run --output table
asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata"

6. App info localizations and privacy policy

asc apps info list --app "APP_ID" --output table
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --output table

For subscription or IAP apps, make sure privacy policy URL is populated:

asc app-setup info set --app "APP_ID" --primary-locale "en-US" --privacy-policy-url "https://example.com/privacy"

7. Screenshots

asc screenshots list --version-localization "LOC_ID" --output table
asc screenshots sizes --output table
asc screenshots validate --path "./screenshots" --device-type "IPHONE_65" --output table

8. Digital goods readiness

asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output table

Use JSON when you need exact diagnostics:

asc validate subscriptions --app "APP_ID" --output json --pretty

9. App Privacy advisory

The public API cannot fully verify App Privacy publish state. If validation reports an advisory, use the experimental web-session flow or confirm manually.

asc web privacy pull --app "APP_ID" --out "./privacy.json"
asc web privacy plan --app "APP_ID" --file "./privacy.json"
asc web privacy apply --app "APP_ID" --file "./privacy.json"
asc web privacy publish --app "APP_ID" --confirm

Manual fallback:

https://appstoreconnect.apple.com/apps/APP_ID/appPrivacy

Submit

Submit a prepared version

Use asc review submit for explicit App Store review submission:

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

Use --version-id "VERSION_ID" when you have already resolved the version.

Upload and submit in one flow

asc publish appstore --app "APP_ID" --ipa "./App.ipa" --version "1.2.3" --submit --dry-run --output table
asc publish appstore --app "APP_ID" --ipa "./App.ipa" --version "1.2.3" --submit --confirm

Add --wait when the command should wait for build processing.

Multi-item review submissions

Use the lower-level review-submission API when the submission needs multiple review items, such as Game Center component versions:

asc review submissions-create --app "APP_ID" --platform IOS
asc review items-add --submission "SUBMISSION_ID" --item-type appStoreVersions --item-id "VERSION_ID"
asc review items-add --submission "SUBMISSION_ID" --item-type gameCenterChallengeVersions --item-id "GC_CHALLENGE_VERSION_ID"
asc review submissions-submit --id "SUBMISSION_ID" --confirm

Monitor

asc status --app "APP_ID"
asc submit status --id "SUBMISSION_ID"
asc submit status --version-id "VERSION_ID"
asc review submissions-list --app "APP_ID" --paginate

Cancel and retry

asc submit cancel --id "SUBMISSION_ID" --confirm
asc submit cancel --version-id "VERSION_ID" --app "APP_ID" --confirm
asc review submissions-cancel --id "SUBMISSION_ID" --confirm

Fix validation issues, then submit again with asc review submit or asc publish appstore --submit --confirm.

Common submission errors

Version is not in valid state

Check:

  1. Build is attached and VALID.
  2. Encryption declaration is resolved or exempt.
  3. Content rights declaration is set.
  4. Required localizations and screenshots are present.
  5. Review details are present.
  6. Pricing and availability exist.
  7. App Privacy has been reviewed and published in App Store Connect.

Export compliance must be approved

Either upload export compliance documentation or rebuild with exempt encryption metadata if that accurately describes the app.

Multiple app infos found

Use the exact app-info ID:

asc apps info list --app "APP_ID" --output table

Notes

  • Do not use legacy submit-preflight or submit-create shortcuts; they are removed.
  • Use asc validate for readiness.
  • Use asc review submit for prepared-version submission.
  • Use asc publish appstore --submit --confirm for high-level upload plus submission.
  • App Privacy publish state is not fully verifiable through the public API.
  • Use --output table for human status and JSON for automation.
  • macOS submissions follow the same review flow but use --platform MAC_OS.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.