Back to Details

expo-build-preflight

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Expo Production Preflight Workflow

Expo 生产构建预检工作流

Follow these steps sequentially to audit the Expo project before a production build. Respond with 
[PASS]
, 
[FAIL]
, or 
[WARN]
for each evaluated item.
请按以下顺序执行步骤，在生产构建前审核Expo项目。对每个评估项返回
[PASS]
、
[FAIL]
或
[WARN]
。

Step 1: Programmatic Validation (Deterministic)

步骤1：程序化验证（确定性）

Execute the validation scripts on the project files.
  1. Run 
    node scripts/validate_expo_config.js <path-to-app.json> <path-to-eas.json>
    .
    • Expected: 
      autoIncrement
      is true, 
      runtimeVersion
      uses fingerprint policy, New Architecture is enabled (SDK 55+), and target SDKs are correct.
  2. Run 
    node scripts/check_assets.js <path-to-assets-folder>
    .
    • Expected: Icons are 1024x1024, no transparent backgrounds on Android adaptive icons.
在项目文件上执行验证脚本。
  1. 运行 
    node scripts/validate_expo_config.js <path-to-app.json> <path-to-eas.json>
    。
    • 预期结果： 
      autoIncrement
      设为true，
      runtimeVersion
      使用指纹策略，已启用New Architecture（SDK 55+），且目标SDK配置正确。
  2. 运行 
    node scripts/check_assets.js <path-to-assets-folder>
    。
    • 预期结果： 图标尺寸为1024x1024，Android自适应图标无透明背景。

Step 2: Platform-Specific Checks (Contextual)

步骤2：平台特定检查（上下文相关）

Review platform-specific configurations based on the build target.
  • For Android builds: Read 
    references/android-rules.md
    to validate API 35 compliance, 16KB page size alignment, and required permissions.
  • For iOS builds: Read 
    references/ios-rules.md
    to validate 
    PrivacyInfo.xcprivacy
    entries, 
    Info.plist
    permission strings, and deployment targets.
根据构建目标审查平台特定配置。
  • 针对Android构建： 阅读 
    references/android-rules.md
    以验证API 35合规性、16KB页面大小对齐情况及所需权限。
  • 针对iOS构建： 阅读 
    references/ios-rules.md
    以验证 
    PrivacyInfo.xcprivacy
    条目、
    Info.plist
    权限字符串及部署目标。

Step 3: Third-Party & Environment Checks

步骤3：第三方服务与环境检查

If the project uses external services (Firebase, Sentry, AI features, Monetization), read 
references/third-party-services.md
.
  • Ensure 
    google-services.json
    and 
    GoogleService-Info.plist
    are handled securely via EAS Secrets (Base64), not committed to the repo.
  • Verify AI Transparency consent screens and Paywall EULA/Privacy Policy visibility.
若项目使用外部服务（Firebase、Sentry、AI功能、付费功能），请阅读 
references/third-party-services.md
。
  • 确保 
    google-services.json
    和 
    GoogleService-Info.plist
    通过EAS Secrets（Base64）安全管理，而非提交到代码仓库。
  • 验证AI透明度同意界面和付费墙EULA/隐私政策的可见性。

Final Output

最终输出

Summarize the findings. If any 
[FAIL]
is present, halt the process and provide exact remediation steps.
总结检查结果。若存在任何 
[FAIL]
结果，终止流程并提供具体的修复步骤。