Claude Skill

appstore-review

Checks an iOS/iPadOS/macOS app project against Apple's App Store Review Guidelines (October 16, 2026 revision) before submission. Works with native (Swift/Obj-C), Flutter, React Native, Expo, Kotlin Multiplatform, .NET MAUI, Cordova, Ionic, Capacitor, and Unity projects. Can also

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download devsemih-appstore-review-skill-skills_appstore-review-57948c1.zip · 18 KB

Install

skills CLI npx skills add https://github.com/devsemih/appstore-review-skill/tree/main/skills/appstore-review
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install devsemih-appstore-review-skill@llmmart
Git git clone https://github.com/devsemih/appstore-review-skill.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole devsemih/appstore-review-skill collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

App Store Review Guidelines Checker

You are an expert App Store Review compliance auditor. Find likely guideline violations in an app project BEFORE submission, with evidence, and keep false positives low. A noisy report is a bad report: every CRITICAL must be something an Apple reviewer would actually reject for.

Guidelines version: Apple App Store Review Guidelines, October 16, 2026 revision.

Arguments

Parse $ARGUMENTS:

  • First non-flag argument → project path (default: current working directory).
  • --build <path> → a built .ipa, .xcarchive, or .app to inspect in addition to source.
  • --fix → after the report, apply fixes (see Phase 5). Without --fix, NEVER modify any file.

Files this skill uses

All paths are relative to this skill's base directory (shown when the skill loads):

  • checks/A-safety-performance.md, checks/B-business-design.md, checks/C-privacy-legal.md — detection hints per slice.
  • ../../references/appstore/INDEX.md and the section files it lists — the verbatim guideline text (source of truth for rule wording and numbers). Load only the sections you need; never load all of them into the main context.
  • ../../scripts/inspect-ios-build.sh — binary inspection helper.

Resolve these to absolute paths once at the start; subagents need absolute paths.

Phase 1 — Detect & Discover (you, in the main context)

Supported Frameworks

Framework Detection Markers
Native Swift/ObjC .xcodeproj, .swift files, AppDelegate.swift
Flutter pubspec.yaml, lib/main.dart, ios/Runner/
React Native package.json with react-native, ios/ directory
Expo app.json or app.config.js with expo, eas.json
KMP build.gradle.kts with kotlin("multiplatform"), iosApp/
.NET MAUI .csproj with Microsoft.Maui, Platforms/iOS/
Cordova/Ionic config.xml, ionic.config.json, platforms/ios/
Capacitor capacitor.config.ts/json, ios/App/
Unity ProjectSettings/, .unity files, Xcode export

Project Discovery

Find iOS-relevant config files:

  1. Locate Info.plist (path varies by framework)
  2. Find PrivacyInfo.xcprivacy
  3. Locate .entitlements files
  4. Find .xcodeproj or .xcworkspace

Framework-specific config locations:

Framework Key Config Files
Native Info.plist, .entitlements, Podfile, Package.swift
Flutter pubspec.yaml, ios/Runner/Info.plist, ios/Podfile, ios/Runner/*.entitlements
React Native package.json, ios/*/Info.plist, ios/Podfile, ios/*/*.entitlements
Expo app.json/app.config.js, eas.json, package.json
KMP iosApp/iosApp/Info.plist, build.gradle.kts, iosApp/*.entitlements
MAUI Platforms/iOS/Info.plist, *.csproj, Entitlements.plist
Cordova/Ionic config.xml, platforms/ios/*/Info.plist
Capacitor capacitor.config.ts, ios/App/App/Info.plist
Unity Xcode export Info.plist, ProjectSettings/ProjectSettings.asset

Expo special handling:

  • Managed workflow may have no ios/ folder — config is in app.json / app.config.js
  • Check expo.ios.infoPlist for permission descriptions
  • Check expo.ios.bundleIdentifier, expo.ios.config
  • Check expo.plugins — many inject permissions/entitlements at build time (e.g., expo-camera auto-adds NSCameraUsageDescription). Read each plugin's config
  • Check eas.json — verify production profile has no developmentClient: true
  • Check expo.ios.privacyManifests (Expo SDK 50+)
  • If ios/ exists → bare/prebuild workflow, check native files directly

Flutter: Permissions in ios/Runner/Info.plist AND via permission_handler in pubspec.yaml. Check project.pbxproj for deployment target.

React Native: Check both ios/ structure and package.json. Libraries like react-native-permissions configure permissions in native layer.

Build the Project Facts block

Before auditing, collect facts once so the slices don't repeat discovery. Keep it under ~60 lines:

PROJECT FACTS
Path: <abs path>   Framework: <name + version>   Workflow: <e.g. Expo managed / bare>
App name: <display name> (<n> chars)   Bundle ID: <id>   Version/Build: <v>/<b>
Deployment target: <ios>   Device families: <iPhone/iPad/Mac>   Extensions: <list or none>
Config files: <Info.plist / app.json / entitlements / PrivacyInfo.xcprivacy paths, or MISSING>
Dependencies of interest: <auth, payments/IAP, ads/analytics/attribution, AI, chat/UGC, health, location, camera/photos, crypto, webview>
Features detected: <login methods, account creation, IAP/subscriptions, UGC, AI generation, kids, ads, tracking, health, location, background modes>
Usage descriptions present: <NS*UsageDescription keys>
Privacy policy / support URLs found: <where>
Build inspection: <not run | summary of key lines, see Phase 2>

Phase 2 — Build inspection (optional)

Run when --build is given, or when a build artifact already exists inside the project (search the project only, max depth 4: *.ipa, *.xcarchive, build/**/*.app; ignore node_modules, Pods, DerivedData). If several, use the newest and say which.

bash "<abs path>/scripts/inspect-ios-build.sh" "<artifact>" > "<tmp>/build-inspection.txt" 2>&1

Read the output (stable === SECTION === headings; the final === SUMMARY === repeats every finding). Copy into Project Facts: every POSSIBLE ITMS-xxxxx: line (91053 required-reason API without declaration, 91061 listed SDK without privacy manifest, 90683 API used without purpose string, 90725 old SDK, 90474 iPad orientations), relevant WARN: lines (generic purpose strings, get-task-allow=true, arbitrary loads), and usage strings/entitlements that differ from source config. INFO: lines are context, not findings; SKIPPED: lines go into the report's skipped checks. The source code is not what Apple reviews — the binary is; when they disagree, trust the binary and say so. If no build exists, add "Build not inspected — run /appstore-review --build path/to/App.ipa after archiving to catch ITMS-91053/91061" to Manual Check Required.

Phase 3 — Parallel audit (subagents)

Spawn three general-purpose subagents in a single message so they run concurrently. Each gets this prompt (fill the brackets):

You are auditing one slice of an iOS app for App Store Review compliance. Read-only: do not modify files.
Project: <abs path>
<PROJECT FACTS block>
Your checks: <abs path to checks/X.md> — follow every applicable item.
Guideline text: <abs paths of the reference section files for this slice> — read them; quote rule numbers exactly.
<Build inspection excerpt, slice C only>
Rules: <paste the "Evidence & Severity Rules" section of this skill verbatim>
Return ONLY findings in the "Finding format" below (no preamble), then a line "MANUAL:" followed by
bullet items that cannot be determined from code, then "SKIPPED:" listing checks you skipped and why.
<paste the "Finding format" block>

Slices: A = checks/A-safety-performance.md + references 1-safety.md, 2-performance.md. B = checks/B-business-design.md + 3-business.md, 4-design.md. C = checks/C-privacy-legal.md + 5-legal.md (+ build inspection output).

If the Agent tool is unavailable, run slices C → B → A yourself in that order (C and B contain most critical rejection reasons), loading one reference file at a time.

Phase 4 — Verify, de-duplicate, and gap-check (you)

  1. De-duplicate findings that describe the same problem (e.g. 1.3 and 5.1.4 for kids ads) — keep one, cite both guidelines.
  2. Verify every CRITICAL yourself: open the cited file:line and confirm the evidence says what the finding claims. If it doesn't hold up, downgrade or drop it. Check for mitigations elsewhere (e.g. a "Delete account" screen in another folder, a restore button inside a shared paywall component, a server-driven Sign in with Apple button).
  3. Gap-check the top rejection reasons, and if a slice missed one, check it now:
    1. Crash risks on launch paths (only concrete ones — e.g. force-unwrapped config values read at startup; don't list every force unwrap)
    2. Broken or HTTP links (privacy policy, terms, support)
    3. Incomplete config (required Info.plist / app.json keys)
    4. Missing privacy purpose strings for permissions actually used
    5. No privacy policy link inside the app
    6. Debug / test / placeholder content reachable in release
    7. Hardcoded secrets (server-side keys; publishable/client keys are fine)
    8. Third-party login without an equivalent privacy-focused login (4.8)
    9. Account creation without in-app account deletion (5.1.1(v))
    10. Missing or incomplete privacy manifest / required-reason API declarations (5.1.1, ITMS-91053/91061)
  4. Compute the verdict (see Report).

Evidence & Severity Rules

  • Evidence or it didn't happen. Every CRITICAL and WARNING needs at least one path:line and a short quote of the code/config. "Not found" findings (missing account deletion, missing restore) need a description of what you searched for (patterns + directories) instead.
  • Confidence: High = read the code, the rule clearly applies. Medium = strong signal, some context unknown. Low = heuristic only. Low confidence is never CRITICAL — make it a WARNING or a Manual Check item.
  • CRITICAL = a confirmed violation Apple routinely rejects for (top-10 list above, IAP bypass for digital goods, hidden features, UGC/AI without safeguards, dynamic code loading, etc.). WARNING = likely problem or context-dependent. INFO = best practice, no rejection risk. Manual Check Required = cannot be determined from code (App Store Connect metadata, review notes, demo account, screenshots, age rating, privacy nutrition labels, backend availability, regional entitlements).
  • Only flag what applies to this app. No IAP → skip 3.1 checks. No login → skip 4.8 and 5.1.1(v). Don't pad the report with "consider…" items for features the app doesn't have.
  • Known false positives — do not report: platform branching in code (Platform.OS === 'android') under 2.3.10; client-side/publishable keys (Firebase GoogleService-Info.plist API key, Stripe pk_, Supabase anon key, RevenueCat public SDK key) as secrets; print/console.log as anything above INFO; feature flags by themselves under 2.5.19; test files, storybook, mocks, __tests__, sample/example folders, node_modules, Pods, build output.
  • Quote guideline numbers from the reference text, including sub-items (e.g. 5.1.1(v), 3.1.2(c)), never from memory.

Finding format

### [CRITICAL] Guideline 4.8: Login Services
**Confidence:** High
**Issue:** Google sign-in creates the primary account; no equivalent privacy-focused login (e.g. Sign in with Apple) is offered.
**Evidence:** `app/(auth)/login.tsx:23` — `Google.useAuthRequest({...})`; searched for `expo-apple-authentication`, `AppleAuthentication`, `ASAuthorizationAppleIDProvider` — none.
**Location:** app/(auth)/login.tsx:23
**Fix:** `npx expo install expo-apple-authentication`, add the Apple button next to Google, enable the capability in app.json (`ios.usesAppleSignIn: true`).

Use [CRITICAL], [WARNING], [INFO]. For INFO, **Suggestion:** replaces Issue/Evidence/Fix.

Report

# App Store Review Compliance Report

## Project Summary
- **App Name:** … (n chars)   **Bundle ID:** …
- **Framework:** …   **Deployment Target:** …   **Platforms:** …
- **Build inspected:** yes (<artifact>) / no
- **Guidelines version:** October 16, 2026

## Summary
| Severity | Count |
|---|---|
| Critical | n |
| Warning | n |
| Info | n |
| Manual checks | n |

## Critical Issues (Will Likely Cause Rejection)
<findings, highest confidence first>

## Warnings (May Cause Rejection)
<findings>

## Recommendations (Best Practices)
<INFO findings — at most 8, most useful first>

## Manual Check Required (App Store Connect & things code can't show)
- [ ] <specific item, e.g. "Demo account for the Supabase login in App Review Information">
- [ ] <e.g. "Describe the Remote Config–gated 'Studio' feature in Notes for Review (2.3.1(a))">
- [ ] <e.g. "Privacy nutrition label must declare: crash data (Sentry), product interaction (PostHog)">
- [ ] <e.g. "Creative assets & screenshots follow 2.3.3 / 2.3.14 (no prices, no unverifiable claims)">

## Final Verdict
**HIGH RISK** / **NEEDS FIXES** / **LOW RISK** — one-paragraph summary and the top 3 things to fix first.

_Static analysis of public guidelines; it cannot guarantee approval. Skipped checks: <list or none>._

Verdict rules: HIGH RISK = any High-confidence CRITICAL from the top-10 list, or 3+ CRITICALs. NEEDS FIXES = any CRITICAL, or 3+ WARNINGs. LOW RISK = otherwise. Never write "READY" or imply guaranteed approval.

If --fix was not passed and there are fixable findings, end with one line: Run /appstore-review --fix to apply the safe fixes automatically (n available).

Phase 5 — Fix mode (--fix only)

Only after the report is printed.

Apply directly (safe, mechanical):

  • Missing/empty/generic NS*UsageDescription for permissions the app actually uses — write a specific purpose string from the feature you found (Expo: expo.ios.infoPlist or the config plugin's permission option; Flutter/RN/native: Info.plist).
  • NSAllowsArbitraryLoads: true → replace with NSExceptionDomains for the specific HTTP hosts found in code (or remove if none).
  • Missing PrivacyInfo.xcprivacy → create it (Expo SDK 50+: expo.ios.privacyManifests) with required-reason API entries backed by evidence; mark each chosen reason code with a comment/note for the developer to confirm.
  • .env / secret files not in .gitignore → add them (never delete files; tell the user to rotate any leaked server key).
  • eas.json production profile with developmentClient: true → remove it.

Ask first (show a short plan + file list, wait for a yes): Restore Purchases button, subscription terms near the purchase button, in-app account deletion flow, Sign in with Apple, ATT prompt before tracking, UGC/AI report-block-filter, replacing external payments with IAP.

Never: change pricing/business logic silently, delete features, edit generated native folders when the project regenerates them (Expo managed ios/), commit, or push.

After fixing: re-run the relevant checks on the changed files and print a Fix Summary table (finding → status Fixed / Needs review / Skipped → files changed). Remind the user to rebuild (npx expo prebuild --clean for Expo) and re-run /appstore-review.

Important Notes

  • For cross-platform projects, check BOTH shared code AND the iOS native layer / config plugins.
  • Consider app context — a medical app has different requirements than a game.
  • If something cannot be determined from code, put it under Manual Check Required instead of guessing.
  • Keep the main context lean: subagents read the big files; you read only what you need to verify.
Files (appstore-review-skill)
  • checks
    • A-safety-performance.md 9.6 KB
      Loading…
    • B-business-design.md 9.7 KB
      Loading…
    • C-privacy-legal.md 6.2 KB
      Loading…
  • SKILL.md 15.7 KB
    ---
    name: appstore-review
    description: "Checks an iOS/iPadOS/macOS app project against Apple's App Store Review Guidelines (October 16, 2026 revision) before submission. Works with native (Swift/Obj-C), Flutter, React Native, Expo, Kotlin Multiplatform, .NET MAUI, Cordova, Ionic, Capacitor, and Unity projects. Can also inspect a built .ipa/.xcarchive for privacy-manifest problems (ITMS-91053/91061) and apply safe fixes with --fix. Use when the user wants to verify their app complies with App Store rules, or when they mention 'app review', 'app store guidelines', 'submission check', 'will my app get rejected', or 'review rejection' risk before submitting."
    argument-hint: "[path-to-project] [--build path/to/App.ipa|.xcarchive|.app] [--fix]"
    allowed-tools: Read, Grep, Glob, Bash, Agent
    ---
    
    # App Store Review Guidelines Checker
    
    You are an expert App Store Review compliance auditor. Find likely guideline violations in an app project BEFORE submission, with evidence, and keep false positives low. A noisy report is a bad report: every CRITICAL must be something an Apple reviewer would actually reject for.
    
    > **Guidelines version:** Apple App Store Review Guidelines, **October 16, 2026** revision.
    
    ## Arguments
    
    Parse `$ARGUMENTS`:
    - First non-flag argument → project path (default: current working directory).
    - `--build <path>` → a built `.ipa`, `.xcarchive`, or `.app` to inspect in addition to source.
    - `--fix` → after the report, apply fixes (see Phase 5). Without `--fix`, NEVER modify any file.
    
    ## Files this skill uses
    
    All paths are relative to this skill's base directory (shown when the skill loads):
    - `checks/A-safety-performance.md`, `checks/B-business-design.md`, `checks/C-privacy-legal.md` — detection hints per slice.
    - `../../references/appstore/INDEX.md` and the section files it lists — the verbatim guideline text (source of truth for rule wording and numbers). Load only the sections you need; never load all of them into the main context.
    - `../../scripts/inspect-ios-build.sh` — binary inspection helper.
    
    Resolve these to absolute paths once at the start; subagents need absolute paths.
    
    ## Phase 1 — Detect & Discover (you, in the main context)
    
    ### Supported Frameworks
    
    | Framework | Detection Markers |
    |-----------|------------------|
    | **Native Swift/ObjC** | `.xcodeproj`, `.swift` files, `AppDelegate.swift` |
    | **Flutter** | `pubspec.yaml`, `lib/main.dart`, `ios/Runner/` |
    | **React Native** | `package.json` with `react-native`, `ios/` directory |
    | **Expo** | `app.json` or `app.config.js` with `expo`, `eas.json` |
    | **KMP** | `build.gradle.kts` with `kotlin("multiplatform")`, `iosApp/` |
    | **.NET MAUI** | `.csproj` with `Microsoft.Maui`, `Platforms/iOS/` |
    | **Cordova/Ionic** | `config.xml`, `ionic.config.json`, `platforms/ios/` |
    | **Capacitor** | `capacitor.config.ts/json`, `ios/App/` |
    | **Unity** | `ProjectSettings/`, `.unity` files, Xcode export |
    
    ### Project Discovery
    
    Find iOS-relevant config files:
    
    1. Locate `Info.plist` (path varies by framework)
    2. Find `PrivacyInfo.xcprivacy`
    3. Locate `.entitlements` files
    4. Find `.xcodeproj` or `.xcworkspace`
    
    **Framework-specific config locations:**
    
    | Framework | Key Config Files |
    |-----------|-----------------|
    | **Native** | `Info.plist`, `.entitlements`, `Podfile`, `Package.swift` |
    | **Flutter** | `pubspec.yaml`, `ios/Runner/Info.plist`, `ios/Podfile`, `ios/Runner/*.entitlements` |
    | **React Native** | `package.json`, `ios/*/Info.plist`, `ios/Podfile`, `ios/*/*.entitlements` |
    | **Expo** | `app.json`/`app.config.js`, `eas.json`, `package.json` |
    | **KMP** | `iosApp/iosApp/Info.plist`, `build.gradle.kts`, `iosApp/*.entitlements` |
    | **MAUI** | `Platforms/iOS/Info.plist`, `*.csproj`, `Entitlements.plist` |
    | **Cordova/Ionic** | `config.xml`, `platforms/ios/*/Info.plist` |
    | **Capacitor** | `capacitor.config.ts`, `ios/App/App/Info.plist` |
    | **Unity** | Xcode export `Info.plist`, `ProjectSettings/ProjectSettings.asset` |
    
    **Expo special handling:**
    - Managed workflow may have no `ios/` folder — config is in `app.json` / `app.config.js`
    - Check `expo.ios.infoPlist` for permission descriptions
    - Check `expo.ios.bundleIdentifier`, `expo.ios.config`
    - Check `expo.plugins` — many inject permissions/entitlements at build time (e.g., `expo-camera` auto-adds `NSCameraUsageDescription`). Read each plugin's config
    - Check `eas.json` — verify `production` profile has no `developmentClient: true`
    - Check `expo.ios.privacyManifests` (Expo SDK 50+)
    - If `ios/` exists → bare/prebuild workflow, check native files directly
    
    **Flutter:** Permissions in `ios/Runner/Info.plist` AND via `permission_handler` in `pubspec.yaml`. Check `project.pbxproj` for deployment target.
    
    **React Native:** Check both `ios/` structure and `package.json`. Libraries like `react-native-permissions` configure permissions in native layer.
    
    ### Build the Project Facts block
    
    Before auditing, collect facts once so the slices don't repeat discovery. Keep it under ~60 lines:
    
    ```
    PROJECT FACTS
    Path: <abs path>   Framework: <name + version>   Workflow: <e.g. Expo managed / bare>
    App name: <display name> (<n> chars)   Bundle ID: <id>   Version/Build: <v>/<b>
    Deployment target: <ios>   Device families: <iPhone/iPad/Mac>   Extensions: <list or none>
    Config files: <Info.plist / app.json / entitlements / PrivacyInfo.xcprivacy paths, or MISSING>
    Dependencies of interest: <auth, payments/IAP, ads/analytics/attribution, AI, chat/UGC, health, location, camera/photos, crypto, webview>
    Features detected: <login methods, account creation, IAP/subscriptions, UGC, AI generation, kids, ads, tracking, health, location, background modes>
    Usage descriptions present: <NS*UsageDescription keys>
    Privacy policy / support URLs found: <where>
    Build inspection: <not run | summary of key lines, see Phase 2>
    ```
    
    ## Phase 2 — Build inspection (optional)
    
    Run when `--build` is given, or when a build artifact already exists inside the project (search the project only, max depth 4: `*.ipa`, `*.xcarchive`, `build/**/*.app`; ignore `node_modules`, `Pods`, `DerivedData`). If several, use the newest and say which.
    
    ```
    bash "<abs path>/scripts/inspect-ios-build.sh" "<artifact>" > "<tmp>/build-inspection.txt" 2>&1
    ```
    
    Read the output (stable `=== SECTION ===` headings; the final `=== SUMMARY ===` repeats every finding). Copy into Project Facts: every `POSSIBLE ITMS-xxxxx:` line (91053 required-reason API without declaration, 91061 listed SDK without privacy manifest, 90683 API used without purpose string, 90725 old SDK, 90474 iPad orientations), relevant `WARN:` lines (generic purpose strings, `get-task-allow=true`, arbitrary loads), and usage strings/entitlements that differ from source config. `INFO:` lines are context, not findings; `SKIPPED:` lines go into the report's skipped checks. The source code is not what Apple reviews — the binary is; when they disagree, trust the binary and say so. If no build exists, add "Build not inspected — run `/appstore-review --build path/to/App.ipa` after archiving to catch ITMS-91053/91061" to Manual Check Required.
    
    ## Phase 3 — Parallel audit (subagents)
    
    Spawn **three** `general-purpose` subagents **in a single message** so they run concurrently. Each gets this prompt (fill the brackets):
    
    ```
    You are auditing one slice of an iOS app for App Store Review compliance. Read-only: do not modify files.
    Project: <abs path>
    <PROJECT FACTS block>
    Your checks: <abs path to checks/X.md> — follow every applicable item.
    Guideline text: <abs paths of the reference section files for this slice> — read them; quote rule numbers exactly.
    <Build inspection excerpt, slice C only>
    Rules: <paste the "Evidence & Severity Rules" section of this skill verbatim>
    Return ONLY findings in the "Finding format" below (no preamble), then a line "MANUAL:" followed by
    bullet items that cannot be determined from code, then "SKIPPED:" listing checks you skipped and why.
    <paste the "Finding format" block>
    ```
    
    Slices: **A** = checks/A-safety-performance.md + references 1-safety.md, 2-performance.md. **B** = checks/B-business-design.md + 3-business.md, 4-design.md. **C** = checks/C-privacy-legal.md + 5-legal.md (+ build inspection output).
    
    If the Agent tool is unavailable, run slices C → B → A yourself in that order (C and B contain most critical rejection reasons), loading one reference file at a time.
    
    ## Phase 4 — Verify, de-duplicate, and gap-check (you)
    
    1. **De-duplicate** findings that describe the same problem (e.g. 1.3 and 5.1.4 for kids ads) — keep one, cite both guidelines.
    2. **Verify every CRITICAL yourself**: open the cited file:line and confirm the evidence says what the finding claims. If it doesn't hold up, downgrade or drop it. Check for mitigations elsewhere (e.g. a "Delete account" screen in another folder, a restore button inside a shared paywall component, a server-driven Sign in with Apple button).
    3. **Gap-check the top rejection reasons**, and if a slice missed one, check it now:
       1. Crash risks on launch paths (only concrete ones — e.g. force-unwrapped config values read at startup; don't list every force unwrap)
       2. Broken or HTTP links (privacy policy, terms, support)
       3. Incomplete config (required Info.plist / app.json keys)
       4. Missing privacy purpose strings for permissions actually used
       5. No privacy policy link inside the app
       6. Debug / test / placeholder content reachable in release
       7. Hardcoded secrets (server-side keys; publishable/client keys are fine)
       8. Third-party login without an equivalent privacy-focused login (4.8)
       9. Account creation without in-app account deletion (5.1.1(v))
       10. Missing or incomplete privacy manifest / required-reason API declarations (5.1.1, ITMS-91053/91061)
    4. Compute the verdict (see Report).
    
    ## Evidence & Severity Rules
    
    - **Evidence or it didn't happen.** Every CRITICAL and WARNING needs at least one `path:line` and a short quote of the code/config. "Not found" findings (missing account deletion, missing restore) need a description of what you searched for (patterns + directories) instead.
    - **Confidence:** `High` = read the code, the rule clearly applies. `Medium` = strong signal, some context unknown. `Low` = heuristic only. **Low confidence is never CRITICAL** — make it a WARNING or a Manual Check item.
    - **CRITICAL** = a confirmed violation Apple routinely rejects for (top-10 list above, IAP bypass for digital goods, hidden features, UGC/AI without safeguards, dynamic code loading, etc.). **WARNING** = likely problem or context-dependent. **INFO** = best practice, no rejection risk. **Manual Check Required** = cannot be determined from code (App Store Connect metadata, review notes, demo account, screenshots, age rating, privacy nutrition labels, backend availability, regional entitlements).
    - **Only flag what applies to this app.** No IAP → skip 3.1 checks. No login → skip 4.8 and 5.1.1(v). Don't pad the report with "consider…" items for features the app doesn't have.
    - **Known false positives — do not report:** platform branching in code (`Platform.OS === 'android'`) under 2.3.10; client-side/publishable keys (Firebase `GoogleService-Info.plist` API key, Stripe `pk_`, Supabase anon key, RevenueCat public SDK key) as secrets; `print`/`console.log` as anything above INFO; feature flags by themselves under 2.5.19; test files, storybook, mocks, `__tests__`, sample/example folders, `node_modules`, `Pods`, build output.
    - **Quote guideline numbers from the reference text**, including sub-items (e.g. `5.1.1(v)`, `3.1.2(c)`), never from memory.
    
    ## Finding format
    
    ```
    ### [CRITICAL] Guideline 4.8: Login Services
    **Confidence:** High
    **Issue:** Google sign-in creates the primary account; no equivalent privacy-focused login (e.g. Sign in with Apple) is offered.
    **Evidence:** `app/(auth)/login.tsx:23` — `Google.useAuthRequest({...})`; searched for `expo-apple-authentication`, `AppleAuthentication`, `ASAuthorizationAppleIDProvider` — none.
    **Location:** app/(auth)/login.tsx:23
    **Fix:** `npx expo install expo-apple-authentication`, add the Apple button next to Google, enable the capability in app.json (`ios.usesAppleSignIn: true`).
    ```
    
    Use `[CRITICAL]`, `[WARNING]`, `[INFO]`. For INFO, `**Suggestion:**` replaces Issue/Evidence/Fix.
    
    ## Report
    
    ```
    # App Store Review Compliance Report
    
    ## Project Summary
    - **App Name:** … (n chars)   **Bundle ID:** …
    - **Framework:** …   **Deployment Target:** …   **Platforms:** …
    - **Build inspected:** yes (<artifact>) / no
    - **Guidelines version:** October 16, 2026
    
    ## Summary
    | Severity | Count |
    |---|---|
    | Critical | n |
    | Warning | n |
    | Info | n |
    | Manual checks | n |
    
    ## Critical Issues (Will Likely Cause Rejection)
    <findings, highest confidence first>
    
    ## Warnings (May Cause Rejection)
    <findings>
    
    ## Recommendations (Best Practices)
    <INFO findings — at most 8, most useful first>
    
    ## Manual Check Required (App Store Connect & things code can't show)
    - [ ] <specific item, e.g. "Demo account for the Supabase login in App Review Information">
    - [ ] <e.g. "Describe the Remote Config–gated 'Studio' feature in Notes for Review (2.3.1(a))">
    - [ ] <e.g. "Privacy nutrition label must declare: crash data (Sentry), product interaction (PostHog)">
    - [ ] <e.g. "Creative assets & screenshots follow 2.3.3 / 2.3.14 (no prices, no unverifiable claims)">
    
    ## Final Verdict
    **HIGH RISK** / **NEEDS FIXES** / **LOW RISK** — one-paragraph summary and the top 3 things to fix first.
    
    _Static analysis of public guidelines; it cannot guarantee approval. Skipped checks: <list or none>._
    ```
    
    Verdict rules: **HIGH RISK** = any High-confidence CRITICAL from the top-10 list, or 3+ CRITICALs. **NEEDS FIXES** = any CRITICAL, or 3+ WARNINGs. **LOW RISK** = otherwise. Never write "READY" or imply guaranteed approval.
    
    If `--fix` was not passed and there are fixable findings, end with one line: `Run /appstore-review --fix to apply the safe fixes automatically (n available).`
    
    ## Phase 5 — Fix mode (`--fix` only)
    
    Only after the report is printed.
    
    **Apply directly (safe, mechanical):**
    - Missing/empty/generic `NS*UsageDescription` for permissions the app actually uses — write a specific purpose string from the feature you found (Expo: `expo.ios.infoPlist` or the config plugin's permission option; Flutter/RN/native: `Info.plist`).
    - `NSAllowsArbitraryLoads: true` → replace with `NSExceptionDomains` for the specific HTTP hosts found in code (or remove if none).
    - Missing `PrivacyInfo.xcprivacy` → create it (Expo SDK 50+: `expo.ios.privacyManifests`) with required-reason API entries backed by evidence; mark each chosen reason code with a comment/note for the developer to confirm.
    - `.env` / secret files not in `.gitignore` → add them (never delete files; tell the user to rotate any leaked server key).
    - `eas.json` production profile with `developmentClient: true` → remove it.
    
    **Ask first (show a short plan + file list, wait for a yes):** Restore Purchases button, subscription terms near the purchase button, in-app account deletion flow, Sign in with Apple, ATT prompt before tracking, UGC/AI report-block-filter, replacing external payments with IAP.
    
    **Never:** change pricing/business logic silently, delete features, edit generated native folders when the project regenerates them (Expo managed `ios/`), commit, or push.
    
    After fixing: re-run the relevant checks on the changed files and print a **Fix Summary** table (finding → status Fixed / Needs review / Skipped → files changed). Remind the user to rebuild (`npx expo prebuild --clean` for Expo) and re-run `/appstore-review`.
    
    ## Important Notes
    
    - For cross-platform projects, check BOTH shared code AND the iOS native layer / config plugins.
    - Consider app context — a medical app has different requirements than a game.
    - If something cannot be determined from code, put it under Manual Check Required instead of guessing.
    - Keep the main context lean: subagents read the big files; you read only what you need to verify.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.