appstore-review

Audits iOS projects for App Store review rejection risks across code, entitlements, and submission metadata.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill appstore-review-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: appstore-review
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/appstore-review
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill appstore-review-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? About 25% of App Store submissions get rejected, often for well-documented but easy-to-miss issues like missing privacy manifest declarations, incomplete subscription disclosures, or metadata gaps. This Skill runs a structured readiness audit on your iOS project before you submit, ordered by real rejection frequency from Apple's 2024 Transparency Report. ## Core Features & Use Cases - Code & Entitlements Audit: Checks app completeness, PrivacyInfo.xcprivacy Required Reason API declarations, StoreKit 2 subscription paywall disclosures, pre-permission priming copy, ATS, export compliance, and entitlements. - Submission Metadata Checklist: Validates App Store Connect fields, screenshot pixel specs, age rating, review notes, and review submission assembly rules (e.g., first-ever IAP must ride with the version submission). - Use Case: Before submitting a SwiftUI app with auto-renewable subscriptions, run the audit to catch a missing Restore Purchases button, an incorrect IAP review screenshot size, or a UserDefaults usage lacking a privacy manifest reason code. ## Quick Start Ask your AI agent to run the appstore-review audit on this iOS project and report every check as PASS, WARN, or FAIL with a summary table.

Frequently Asked Questions about appstore-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my iOS app for App Store rejection risks before submitting?▼

Run the appstore-review audit from your project directory. It inspects Swift source, Info.plist, entitlements, privacy manifests, and paywall UI, then reports each check as PASS, WARN, or FAIL with a summary table of critical issues.

What privacy manifest requirements does App Store review enforce?▼

Since May 2024, apps must include PrivacyInfo.xcprivacy declaring all Required Reason API usage across five categories: file timestamps, system boot time, disk space, active keyboards, and UserDefaults. Missing declarations trigger automated ITMS-91053 rejections before human review.

Does the audit work for apps without subscriptions or in-app purchases?▼

Yes. The skill detects StoreKit usage before evaluating compliance, so IAP and paywall checks report PASS as not applicable for apps without subscriptions. Push notification and IDFA checks similarly skip gracefully when those features are absent.

Why was my app rejected under Guideline 2.1(b) for in-app purchases?▼

The first-ever IAP must be attached to the same review submission as the app version. Submitting the version alone while products sit in Prepare for Submission triggers a 2.1(b) rejection, and Apple's remedy requires resubmitting the IAPs plus a new binary.

What paywall disclosures does Apple require for auto-renewable subscriptions?▼

The paywall must show subscription name and duration, full renewal price as the most prominent element, trial terms, tappable Terms of Use and Privacy Policy links, a Restore Purchases mechanism, and auto-renewal language. Terms and privacy links must also appear in App Store Connect metadata.