Automate this: /mobile-release:preflight runs this audit against the real project and reports
BLOCK/RISK/CLEAR with no uploads; --fix applies the repo-level fixes. It needs no credentials, which
makes it the first thing to run in a session with no store access.
Decide whether pressing Submit for Review is safe, and say exactly what to change if it is not. Work through every section in order and give each a verdict of BLOCK, RISK, or CLEAR. Do not ask which sections to run — run them all, against the real project, using the commands given rather than by reading code and guessing.
Uploading the binary is the app-store-publish skill. Producing screenshots and preview videos is store-screenshots and store-preview-videos. This skill only decides whether the thing you already built will pass.
Confidence marks used throughout this skill and its references: [verified] — read off a primary vendor source on 2026-08-05. [snippet] — secondary source only, plausible but unconfirmed. [unverified] — not confirmed anywhere; check it before relying on it.
Review-readiness process:
- Locate the app target's
Info.plist,.xcodeproj/.xcworkspace, entitlements, andPrivacyInfo.xcprivacy. Everything below reads from these paths. - Run the sweep in 1. Checks you can run. Record each result; do not summarise from memory.
- Check assets and metadata against 2; full tables in
references/metadata-limits.md. - Check privacy against 3; reason codes and the SDK list in
references/privacy.md. - Check guideline exposure — 4, expanded in
references/guidelines.md. - Draft the App Review notes — 5, templates in
references/review-notes.md. - Sweep the preemptable rejections in
references/rejections.md, then emit the verdict table in Output Format. A single BLOCK means do not submit.
Load only the reference you need.
Contents
- 1. Checks you can run
- 2. Assets and metadata
- 3. Privacy declarations
- 4. Guideline exposure
- 5. App Review notes
- 6. Rejections worth preempting
- 7. Keeping this current
- Output Format
- References
1. Checks you can run
Run these from the project root. Each one either produces evidence or proves an absence — both are results.
PLIST="MyApp/Info.plist" # adjust; find it with: find . -name Info.plist -not -path '*/Pods/*'
# Every purpose string currently declared
plutil -p "$PLIST" | grep -i UsageDescription
# Every permission-gated framework the code actually touches
grep -rEn "AVCaptureDevice|PHPhotoLibrary|CLLocationManager|CNContactStore|EKEventStore|CMMotionManager|LAContext|ATTrackingManager|SFSpeechRecognizer|HKHealthStore|CBCentralManager" \
--include=*.swift --include=*.m --include=*.mm . | grep -v /Pods/
# Placeholder text, unfinished work, and staging leakage a reviewer could hit
grep -rniE "lorem ipsum|coming soon|TODO|FIXME|placeholder" --include=*.swift --include=*.strings . | grep -v /Pods/
grep -rnE "https?://(localhost|127\.0\.0\.1|.*staging|.*\.test)" --include=*.swift --include=*.plist . | grep -v /Pods/
grep -rn "#if DEBUG" --include=*.swift . | grep -v /Pods/
# Privacy manifest present, and what it declares
find . -name PrivacyInfo.xcprivacy -not -path '*/Pods/*' -exec plutil -p {} \;
# ATS exceptions, and export compliance answered up front
plutil -p "$PLIST" | grep -A6 NSAppTransportSecurity
plutil -p "$PLIST" | grep ITSAppUsesNonExemptEncryption
# Declared device families — "1,2" is the Xcode default and makes iPad screenshots mandatory
grep -rn "TARGETED_DEVICE_FAMILY" *.xcodeproj/project.pbxproj
# Account deletion exists if account creation does (5.1.1(v)); icon has no alpha
grep -rniE "delete (my )?account|deleteAccount|accountDeletion" --include=*.swift --include=*.strings .
sips -g hasAlpha -g pixelWidth -g pixelHeight AppIcon-1024.png
Interpreting them: a framework in the second grep with no matching key in the first is a BLOCK — the app crashes on first use of that permission [verified] for ATT, [unverified] as a general rule. Any hit in the placeholder or staging greps that reaches the UI is a guideline 2.1 BLOCK. TARGETED_DEVICE_FAMILY = "1,2" on an iPhone-only product is a RISK: it declares iPad, which makes 13" iPad screenshots required and invites an iPad-layout rejection.
2. Assets and metadata
Specs read off Apple's own pages on 2026-08-05. Apple revises them silently — re-read before a release you care about rather than trusting this table.
Screenshots. 1–10 per display size per localization; .jpeg / .jpg / .png; no alpha channels or transparencies [verified]. There is no 6.7" size in Apple's current list at all — if a tool or checklist asks for one, it is stale.
| Slot | Accepted portrait px | Required? | Confidence |
|---|---|---|---|
| iPhone 6.9" | 1260 × 2736, 1290 × 2796, 1320 × 2868 |
Primary iPhone size — providing it satisfies the iPhone requirement | [verified] |
| iPhone 6.5" | 1284 × 2778, 1242 × 2688 |
Required only if the app runs on iPhone and 6.9" is not provided | [verified] |
| iPad 13" | 2064 × 2752, 2048 × 2732 |
Required if the app runs on iPad | [verified] |
| every smaller iPhone/iPad class | — | Optional; Connect scales the required sets down | required-status [verified], scaling [snippet] |
Landscape is the same numbers transposed. Practical minimum: one 6.9" set, plus a 13" iPad set if the target declares iPad. Full slot table, Mac/TV/Watch/Vision sizes, and how to capture them: the store-screenshots skill (skills/store-screenshots/references/store-slots.md).
App icon. 1024 × 1024 for iOS/iPadOS [verified]. Do not pre-round the corners — the system masks them, and pre-masked layers damage the specular highlight and jag the edges [verified]. Must be opaque, no alpha [snippet]: Apple's current HIG no longer restates it, but a PNG with alpha is rejected.
App previews. 15–30 s, up to 3 per localization, ≤ 500 MB, H.264 or ProRes 422 HQ, ≤ 30 fps [verified]. The upload resolution is not the screenshot resolution: iPhone 6.9"/6.5"/6.3"/6.1" all upload at 886 × 1920 portrait, iPad 13"/11"/10.5" at 1200 × 1600 [verified]. Footage must be screen capture of the app itself (2.3.4) [verified]. Producing them: store-preview-videos.
Character limits — be precise about which of these Apple publishes.
| Field | Limit | Confidence |
|---|---|---|
| App name | 30 characters | [verified] — stated on Apple's product-page reference and in guideline 2.3.7 |
| Subtitle | 30 characters | [verified] |
| Promotional text | 170 characters | [verified] — editable without a new build |
| Keywords | 100 characters total, comma-separated, no spaces after commas | [verified] |
| App Review Notes | 4000 bytes — bytes, not characters | [verified] |
| Description | 4,000 characters | [snippet] — Apple publishes no limit for this field. Universally reported by third parties; treat as a working assumption |
| What's New | 4,000 characters | [snippet] — same caveat |
Apple's "Required, localizable, and editable properties" reference publishes no character limits at all [verified] — it covers required/localizable/editable flags only. Anyone quoting Apple for the 4,000 is quoting a third party. Age rating tiers, required-vs-editable flags, and the full field list: references/metadata-limits.md.
3. Privacy declarations
Four separate artefacts that must all agree with each other and with the binary's real behaviour.
- App Privacy questionnaire (App Store Connect). Three buckets — Data Used to Track You, Data Linked to You, Data Not Linked to You
[verified]. Data collected by your third-party SDKs counts as yours[verified]. Answers can be updated any time without a new submission[verified], so an inaccurate label is never worth leaving in place. PrivacyInfo.xcprivacy. Top-level keys:NSPrivacyTracking,NSPrivacyTrackingDomains,NSPrivacyCollectedDataTypes,NSPrivacyAccessedAPITypes[verified]. Each bundle that uses a required-reason API needs its own manifest — an SDK cannot rely on the app's, and the app cannot rely on an SDK's[verified].- Required-reason APIs. Five categories, each with a fixed set of approved reason codes:
NSPrivacyAccessedAPICategoryFileTimestamp,…SystemBootTime,…DiskSpace,…ActiveKeyboards,…UserDefaults[verified]. All five categories and all 17 codes were read from Apple's JSON endpoint and are listed inreferences/privacy.md. Use only those codes. If a use case is not covered by any of them, the answer is Apple's new-reason request form, not an invented code. Since May 1, 2024 an app that does not describe its required-reason API use "aren't accepted by App Store Connect"[verified]. - Third-party SDK manifests and signatures. Apple publishes a list of SDKs that must ship a privacy manifest and a signature
[verified]. Any Flutter, Firebase, Facebook, or React Native app is almost certainly on it. Full list inreferences/privacy.md.
ATT. If the app calls App Tracking Transparency, NSUserTrackingUsageDescription is mandatory — "if you don't include a usage-description string, your app may crash when a user first launches it" [verified]. Request permission before any tracking occurs, as guideline 5.1.2 requires [verified]. Fingerprinting is never allowed, with or without permission [verified].
Purpose strings. Guideline 5.1.1 requires strings that "clearly and completely describe your use of the data" [verified]. Every permission the binary can request needs its key — linking the framework is enough to require it. Common keys are in references/privacy.md [unverified as a complete list]; the authoritative check is the first grep pair in section 1.
4. Guideline exposure
Each of these is a real rejection with a concrete remedy. Guideline text [verified]; expanded treatment in references/guidelines.md.
| Guideline | What it says | What to do about it |
|---|---|---|
| 2.1 App Completeness | Final versions only, working URLs, no placeholders, tested on device, demo account provided and backend live during review | Put a non-expiring demo account in App Review Information, not in Notes. Keep staging alive through review. A built-in demo mode instead of an account needs Apple's prior approval |
| 2.3 Accurate Metadata | Metadata must reflect the core experience; no hidden or undocumented features; new features described with specificity; screenshots show the app in use; What's New must describe the change | Strip unshipped features and other-platform references (2.3.10) from the description. Replace generic What's New on any feature release (2.3.12). Use fictional account data in screenshots, never real personal data (2.3.9) |
| 3.1.1 In-App Purchase | Digital goods and unlocks must use IAP — no license keys, QR codes, or crypto as unlock mechanisms; purchased currency cannot expire; a restore mechanism is required; loot-box odds must be disclosed | Route every digital unlock through StoreKit and add Restore Purchases. External purchase links are permitted without the entitlement on the US App Store; outside the US, without the entitlement, no external purchase buttons, links, or calls to action |
| 4.2 Minimum Functionality | Must go beyond a repackaged website; must be useful, unique, app-like; not primarily marketing, ads, web clippings, or link collections; must work without requiring another app | If it is a webview wrapper, add native capability the site cannot provide. Disclose download size and prompt before pulling additional resources on first launch (4.2.3). Template/whitelabel apps must be submitted by the content provider (4.2.6) |
| 5.1.1 Data Collection and Storage | Privacy policy in App Store Connect and in the app; consent required even for anonymous collection; data minimization; account deletion in-app where account creation exists; no login gate for functionality unrelated to accounts | Add the delete-account flow, allow use without login, prefer a picker or share sheet over full Photos/Contacts access, and make paid functionality independent of granting data access |
Also check 4.7 if the app hosts mini apps, plug-ins, chatbots, or emulators, and 2.2 if any beta or trial language survived into the release build.
5. App Review notes
The Notes field holds up to 4000 bytes [verified]. Multi-byte characters cost more than one byte each — an emoji-laden note truncates earlier than it looks.
Put in the structured fields, not in Notes: the Sign-in required username and password. Apple's requirement is unambiguous — "the demo account is used during the App Review process and must not expire" [verified]. If the app uses SSO, include a working demo login for that provider too [verified].
Write in Notes: how to reach every gated feature in the fewest taps; any hardware, QR code, or deep link the reviewer needs; a test stream URL if the app delivers streaming video over cellular [verified]; IAP test instructions; and one line naming what changed since a previous rejection.
Explaining a feature that looks like a violation is the highest-value paragraph you will write. Name the guideline yourself, state why the app is on the right side of it, and point at the evidence in the build. A reviewer who has to work out your reasoning unaided will reject and let you explain on appeal. Templates in references/review-notes.md.
Expedited review exists for a critical bug fix (include reproduction steps against the current App Store version) or a launch tied to an event you are directly associated with (name it, date it, state your association) [snippet]. Request at https://developer.apple.com/contact/app-store/?topic=expedite. It is a limited privilege that can be revoked if abused [unverified] — do not spend it on a schedule slip. Around 90% of submissions are reviewed in under 24 hours [snippet], so most schedule slips do not need it.
6. Rejections worth preempting
references/rejections.md lists the failures that generate the most rework, each with a fix. Be honest about that list's provenance: Apple's own common-rejections page rendered empty to every fetch attempted on 2026-08-05, so the list is [unverified] as a ranking — the guideline number attached to each row is verified, the ordering and the "most common" framing are not. Present it as a checklist, never as Apple's published statistics.
7. Keeping this current
developer.apple.com/documentation/ and /design/ pages are single-page apps: a plain fetch returns only a <title>. The readable content is at a JSON endpoint [verified as a technique] — this is how the privacy reason codes in references/privacy.md were obtained, and how to refresh them:
BASE=https://developer.apple.com/tutorials/data
curl -s $BASE/documentation/bundleresources/app-privacy-configuration.json | python3 -m json.tool
curl -s $BASE/design/human-interface-guidelines/app-icons.json | python3 -m json.tool
/help/app-store-connect/… and /app-store/review/guidelines/ are server-rendered and fetch directly; deadlines are posted at https://developer.apple.com/news/upcoming-requirements/. Per-fact source list: references/refresh-sources.md.
Output Format
One verdict table, then BLOCK items with the exact fix, then RISK items, then what to write in Notes. Cite the file and line for every finding. A single BLOCK means do not submit.
Example output:
Submission readiness — Notes 2.7.0 (build 143)
Checked 2026-08-05 against specs verified the same day.
| # | Area | Verdict | Finding |
|---|---|---|---|
| 1 | Executable checks | BLOCK | AVCaptureDevice linked, no NSCameraUsageDescription |
| 2 | Assets and metadata | RISK | iPad declared, no 13" screenshots uploaded |
| 3 | Privacy declarations | BLOCK | PrivacyInfo.xcprivacy missing NSPrivacyAccessedAPICategoryUserDefaults |
| 4 | Guideline exposure | RISK | Account creation exists, no in-app deletion (5.1.1(v)) |
| 5 | App Review notes | BLOCK | No demo account set; the app is behind a login wall |
| 6 | Preemptable rejections | CLEAR | — |
BLOCK — fix before submitting
1. Camera used with no purpose string. Sources/Scanner/ScannerView.swift:41 calls AVCaptureDevice.requestAccess. MyApp/Info.plist declares no camera key, so the app terminates the first time a user taps Scan.
<!-- Add to MyApp/Info.plist -->
<key>NSCameraUsageDescription</key>
<string>Scans receipts so amounts fill in automatically.</string>
2. UserDefaults used without a declared reason. PrivacyInfo.xcprivacy declares only NSPrivacyAccessedAPICategoryFileTimestamp, but SettingsStore.swift:12 uses UserDefaults. Uploads have been rejected on this since 2024-05-01. CA92.1 is the approved code for data accessible only to this app:
<dict>
<key>NSPrivacyAccessedAPIType</key>
<string>NSPrivacyAccessedAPICategoryUserDefaults</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array><string>CA92.1</string></array>
</dict>
3. No demo account. The app opens on a login wall. Create a permanent reviewer account and put it in App Store Connect → App Review Information → Sign-in required. Apple requires a demo account that must not expire.
RISK
- iPad declared but unserved.
project.pbxproj:412setsTARGETED_DEVICE_FAMILY = "1,2", which makes 13" iPad screenshots required (2064 × 2752or2048 × 2732) and puts an iPhone-width layout in front of a reviewer on an iPad. Capture the iPad set withstore-screenshots, or set the family to1. - No in-app account deletion (5.1.1(v)). A settings row calling the existing
DELETE /accountendpoint clears it.
Notes to write
Demo account:
review@example.com/ (in the Sign-in required fields). Tap Scan on the home tab to reach the camera feature — it needs camera access, used only to read receipt totals on-device; nothing is uploaded. Subscriptions: tap Upgrade in Settings; sandbox purchases are enabled and Restore Purchases is at the bottom of that sheet. New in 2.7.0: background sync — create a note offline, reconnect, and it appears on a second device within a minute.
End of example.
References
references/metadata-limits.md— every store field with its limit, its confidence, and whether it is required, localizable, and editable; the age-rating questionnaire tiers and categories; the 4+-appropriate-marketing rule.references/privacy.md— App Privacy data categories and the tracking definition,PrivacyInfo.xcprivacykeys with a worked file, all five required-reason categories and all 17 approved codes, Apple's third-party SDK list, ATT, and the purpose-string key list.references/guidelines.md— 2.1, 2.2, 2.3, 3.1.1, 4.2, 4.7, 5.1.1, and 5.1.2 in full, each with the concrete remedy and how a reviewer detects it.references/review-notes.md— a Notes template, demo-account rules, how to phrase a feature that looks like a violation, attachments, replying to App Review, appeals, and expedited review.references/rejections.md— the ranked rejection list with its honest provenance, each row mapped to a verified guideline number and a fix.references/refresh-sources.md— which Apple URLs are server-rendered, which need the/tutorials/data/…jsonform, and what each is authoritative for.