iOS & Android 双端上架全流程与高通过率避坑指南

关键工程指标 (Key Engineering Metrics)

• 累计成功上架应用 (Commercial Apps Shipped)：20+
• 首轮提审通过率 (First-Pass Approval)：95%+
• 自动化构建发版耗时 (CI/CD Release Pipeline)：15 min

工程落地核查清单 (Architecture Checklist)

• iOS 必配 PrivacyInfo.xcprivacy 隐私清单，逐项对齐 Required Reason API（UserDefaults / 文件时间戳等）
• 提供具备真实业务数据的审核专用演示账号，并在后台关闭审核账号的短信验证码或固定白名单验证码
• 凡含账号体系必须支持「应用内一键注销并清理个人数据」（App Store Guideline 5.1.1(v) 硬性红线）
• 内购与数字权益遵循 IAP / Play Billing 规范，恢复购买（Restore Purchases）按钮清晰可达
• Android 靶向最新 Target SDK，完成 64 位与 16KB 页面对齐检查，配置 Play App Signing 与混淆映射表上传

一、双端上架前必须准备的账号、证书与工程配置

1. Accounts, Signing Certificates & Build Pipeline Preparation

iOS 需提前准备 Apple Developer 账号、Bundle ID、发布证书、描述文件、App 专用密码，并确认账号付款协议、税务和银行业务状态正常。Android 需配置 Keystore 签名、包名、版本号、Google Play App Signing，国内市场还要根据渠道准备软著、隐私检测报告与主体资质。工程阶段应统一环境配置，避免 Debug 权限、测试入口、日志开关和非正式域名混入正式包。

Before building release artifacts, verify Apple Developer DUNS/tax/banking status, Provisioning Profiles, APNs keys, and App Store Connect API keys. On Android, secure the upload keystore and enroll in Google Play App Signing. Use CI/CD flavors to strip debug menus, staging endpoints, and unused permissions from production builds.

二、审核合规材料怎么准备才能显著降低拒审概率

2. Privacy Manifests, Permission Prompts & High-Risk Review Clauses

审核材料的核心是“功能可验证、数据用途可解释、权限申请有依据”。iOS 要准确填写隐私标签、ATT、定位、相机、相册等用途描述，并确保截图、分类、年龄分级与实际功能一致。Android 需重点处理广告标识、存储、定位、后台行为和订阅说明。隐私政策必须覆盖 SDK 清单、数据收集类型、保存期限、用户权利和联系方式；登录、支付、账号删除等路径要能被审核人员直接走通。

Most rejections stem from incomplete review notes, vague NSUsageDescription strings, or unverified third-party SDK privacy manifests. Every permission prompt must explain the concrete user benefit in context. Apps with account creation must include an immediate in-app account deletion workflow and accessible privacy policy URL.

三、提审发布、灰度放量与拒审问题的标准处理流程

3. Phased Rollout, Telemetry Guardrails & Rejection Appeal SOP

发布前应执行真机回归、弱网测试、崩溃检测和支付闭环验证。iOS 建议先通过 TestFlight 覆盖审核场景，提交时填写清晰的审核备注、测试账号和演示视频；Android 可使用内部测试、封闭测试和分阶段发布。上线后按崩溃率、ANR、评分和核心转化逐步放量。若被拒，先定位审核条款，不要盲目重复提交；应提供证据、修复包或解释说明，保持回复具体、克制、可验证。

Always ship with phased release enabled (1% -> 5% -> 20% -> 50% -> 100%) while monitoring crash-free sessions and ANR rates. Attach a 60-second screen recording in App Review Information when hardware peripherals (BLE devices) or complex KYC flows are involved so reviewers can verify full functionality immediately.

参考实现代码 (ios/Runner/PrivacyInfo.xcprivacy)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>NSPrivacyTracking</key>
  <false/>
  <key>NSPrivacyAccessedAPITypes</key>
  <array>
    <dict>
      <key>NSPrivacyAccessedAPIType</key>
      <string>NSPrivacyAccessedAPICategoryUserDefaults</string>
      <key>NSPrivacyAccessedAPITypeReasons</key>
      <array><string>CA92.1</string></array>
    </dict>
  </array>
</dict>
</plist>

常见问题解答 (FAQ)

问：双端同时发布，为什么常常无法同一天过审？ (Why do iOS and Android releases often get approved on different days?)

答：因为 iOS、Google Play 和国内安卓渠道的审核标准、人工复核节奏、资质要求不同。iOS 对账号、订阅、隐私和账号删除审查更严格；国内安卓市场还会核查软著、ICP备案、内容类目和合规检测。建议提前 3 到 7 天提交，并准备审核素材与应急回滚方案。 Apple App Review, Google Play, and regional Android stores operate on independent review queues and policy checks. Submit 3 to 7 days ahead of your target launch date using "Manually release this version" so both platforms can be flipped live simultaneously once approved.