App Store Connect 提交健康检查指南 - 减少审核失败，监控应用状态

asc-submission-health by rudrankriyam/app-store-connect-cli-skills

1,200 周安装量

588 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-submission-health

开发开发运维测试

🇨🇳中文介绍

asc 提交健康检查

使用此技能可减少审核提交失败并监控状态。

前置条件

已配置身份验证并解析应用/版本/构建 ID。
构建已处理（不处于处理状态）。
所有必需的元数据均已完成。

提交前检查清单

1. 验证构建状态

asc builds info --build "BUILD_ID"

检查：

processingState 为 VALID
usesNonExemptEncryption - 如果为 true，则需要加密声明

2. 加密合规性

如果 usesNonExemptEncryption: true：

# 如果应用应豁免，请修补本地 plist 辅助文件，重新构建并重新上传
asc encryption declarations exempt-declare --plist "./Info.plist"

# 列出现有声明
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"

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

3. 内容权利声明

所有 App Store 提交均需此项：

# 检查当前状态
asc apps content-rights view --app "APP_ID"

# 为大多数应用设置
asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false

DOES_NOT_USE_THIRD_PARTY_CONTENT
USES_THIRD_PARTY_CONTENT

# 检查版本详情
asc versions view --version-id "VERSION_ID" --include-build

# 验证版权已设置
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"

5. 本地化已完成

# 列出版本本地化
asc localizations list --version "VERSION_ID"

# 检查必填字段：description, keywords, whatsNew, supportUrl

6. 存在屏幕截图

每个地区都需要目标平台的屏幕截图。

7. 应用信息本地化（隐私政策）

# 列出应用信息 ID（如果存在多个）
asc apps info list --app "APP_ID"

# 检查隐私政策 URL
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"

8. 应用隐私准备情况咨询

asc 可以警告应用隐私准备情况，但公共的 App Store Connect API 无法验证应用隐私是否已完全发布。在最终提交前：

asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc validate --app "APP_ID" --version "1.2.3" --platform IOS

在此技能中进行顶层准备情况检查时，建议使用版本字符串形式，以保持与 asc submit preflight 一致。本指南后面的底层命令在 API 要求的地方仍使用 VERSION_ID。

如果任一命令报告应用隐私咨询，则公共 API 无法验证发布状态。如果您依赖这些端点，请使用 Web 会话隐私工作流：

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

如果您不想使用实验性的 asc web privacy ... 命令，请在 App Store Connect 中手动确认应用隐私：

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

9. 数字商品准备情况（应用内购买 / 订阅）

如果应用销售订阅或应用内购买，请在提交前单独验证：

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

在 0.45.3+ 版本中，asc validate subscriptions 将 MISSING_METADATA 扩展为每个订阅的诊断矩阵。使用它来识别缺失的审核屏幕截图、促销图片、定价或可用性覆盖缺口、优惠准备情况以及应用/构建证据，然后重试提交或首次审核附加。

当您需要机器可读格式的精确地区缺口时，请使用 --output json --pretty。

使用审核提交 API（推荐）

# 创建提交
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 submissions-submit --id "SUBMISSION_ID" --confirm

asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc submit create --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm

当存在多个平台时，请使用 --platform。

# 检查提交状态
asc submit status --id "SUBMISSION_ID"
asc submit status --version-id "VERSION_ID"

# 列出所有提交
asc review submissions-list --app "APP_ID" --paginate

# 取消提交
asc submit cancel --id "SUBMISSION_ID" --confirm

# 或通过审核 API
asc review submissions-cancel --id "SUBMISSION_ID" --confirm

修复问题，然后重新提交。

"版本状态无效"

构建已附加且状态为 VALID
加密声明已批准（或豁免）
内容权利声明已设置
所有本地化已完成
所有地区均存在屏幕截图
应用隐私已在 App Store Connect 中审核并发布

"必须批准出口合规性"

构建的 usesNonExemptEncryption: true。请执行以下操作之一：

上传出口合规性文档
或者在 Info.plist 中设置 ITSAppUsesNonExemptEncryption = NO 后重新构建

"找到多个应用信息"

使用 --app-info 标志并指定正确的应用信息 ID：

asc apps info list --app "APP_ID"

asc submit create 会自动使用新的 reviewSubmissions API。
asc submit preflight 可能返回非阻塞性咨询；请在提交前查看。
应用隐私发布状态无法通过公共 API 验证。
建议使用 asc apps content-rights view/edit 而非临时应用 JSON 检查。
对于 MISSING_METADATA 情况，asc validate subscriptions 现在提供了更丰富的每个订阅诊断信息。
如果您使用 ASC Web 会话流程，asc web privacy pull|plan|apply|publish 是应用隐私的 CLI 路径。
如果您避免使用实验性的 Web 会话命令，请在 App Store Connect 中手动确认应用隐私。
当您需要人类可读的状态时，请使用 --output table。
macOS 提交遵循相同流程，但使用 --platform MAC_OS。

🇺🇸English

asc submission health

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

Preconditions

Auth configured and app/version/build IDs resolved.
Build is processed (not in processing state).
All required metadata is complete.

Pre-submission Checklist

1. Verify Build Status

asc builds info --build "BUILD_ID"

Check:

processingState is VALID
usesNonExemptEncryption - if true, requires encryption declaration

2. Encryption Compliance

If usesNonExemptEncryption: true:

# If the app should be exempt, patch the local plist helper, rebuild, and re-upload
asc encryption declarations exempt-declare --plist "./Info.plist"

# List existing declarations
asc encryption declarations list --app "APP_ID"

# Create declaration if needed
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

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

If the app truly uses only exempt transport encryption, prefer asc encryption declarations exempt-declare --plist "./Info.plist" and rebuild instead of creating a declaration that does not match the binary.

3. Content Rights Declaration

Required for all App Store submissions:

# Check current status
asc apps content-rights view --app "APP_ID"

# Set it for most apps
asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false

Valid values:

DOES_NOT_USE_THIRD_PARTY_CONTENT
USES_THIRD_PARTY_CONTENT

4. Version Metadata

# Check version details
asc versions view --version-id "VERSION_ID" --include-build

# Verify copyright is set
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"

5. Localizations Complete

# List version localizations
asc localizations list --version "VERSION_ID"

# Check required fields: description, keywords, whatsNew, supportUrl

6. Screenshots Present

Each locale needs screenshots for the target platform.

7. App Info Localizations (Privacy Policy)

# List app info IDs (if multiple exist)
asc apps info list --app "APP_ID"

# Check privacy policy URL
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"

8. App Privacy readiness advisory

asc can warn about App Privacy readiness, but the public App Store Connect API cannot verify whether App Privacy is fully published. Before final submission:

asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc validate --app "APP_ID" --version "1.2.3" --platform IOS

Prefer the version string form for top-level readiness checks in this skill so it stays aligned with asc submit preflight. Lower-level commands later in this guide still use VERSION_ID where the API requires it.

If either command reports an App Privacy advisory, the public API cannot verify publish state. Use the web-session privacy workflow if you rely on those endpoints:

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

If you do not want to use the experimental asc web privacy ... commands, confirm App Privacy manually in App Store Connect:

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

9. Digital goods readiness (IAPs / subscriptions)

If the app sells subscriptions or in-app purchases, validate those separately before submit:

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

In 0.45.3+, asc validate subscriptions expands MISSING_METADATA into a per-subscription diagnostics matrix. Use it to identify missing review screenshots, promotional images, pricing or availability coverage gaps, offer readiness, and app/build evidence before retrying submit or first-review attach.

Use --output json --pretty when you want exact territory gaps in machine-readable form.

Submit

Using Review Submissions API (Recommended)

# Create submission
asc review submissions-create --app "APP_ID" --platform IOS

# Add version to submission
asc review items-add \
  --submission "SUBMISSION_ID" \
  --item-type appStoreVersions \
  --item-id "VERSION_ID"

# Submit for review
asc review submissions-submit --id "SUBMISSION_ID" --confirm

Using Submit Command

asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc submit create --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm

Use --platform when multiple platforms exist.

Monitor

# Check submission status
asc submit status --id "SUBMISSION_ID"
asc submit status --version-id "VERSION_ID"

# List all submissions
asc review submissions-list --app "APP_ID" --paginate

Cancel / Retry

# Cancel submission
asc submit cancel --id "SUBMISSION_ID" --confirm

# Or via review API
asc review submissions-cancel --id "SUBMISSION_ID" --confirm

Fix issues, then re-submit.

Common Submission Errors

"Version is not in valid state"

Check:

Build is attached and VALID
Encryption declaration approved (or exempt)
Content rights declaration set
All localizations complete
Screenshots present for all locales
App Privacy has been reviewed and published in App Store Connect

"Export compliance must be approved"

The build has usesNonExemptEncryption: true. Either:

Upload export compliance documentation
Or rebuild with ITSAppUsesNonExemptEncryption = NO in Info.plist

"Multiple app infos found"

Use --app-info flag with the correct app info ID:

asc apps info list --app "APP_ID"

Notes

asc submit create uses the new reviewSubmissions API automatically.
asc submit preflight can return non-blocking advisories; review them before submitting.
App Privacy publish state is not verifiable via the public API.
Prefer asc apps content-rights view/edit over ad-hoc app JSON inspection.
asc validate subscriptions now provides much richer per-subscription diagnostics for MISSING_METADATA cases.
If you use ASC web-session flows, asc web privacy pull|plan|apply|publish is the CLI path for App Privacy.
If you avoid the experimental web-session commands, confirm App Privacy manually in App Store Connect.
Use --output table when you want human-readable status.
macOS submissions follow the same process but use --platform MAC_OS.

Weekly Installs

1.2K

Repository

rudrankriyam/ap…i-skills

GitHub Stars

588

First Seen

Jan 28, 2026

Security Audits

Gen Agent Trust HubPass SocketWarn SnykPass

Installed on

codex1.2K

opencode1.2K

gemini-cli1.2K

github-copilot1.1K

kimi-cli1.1K

amp1.1K

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

102,200 周安装