ios-app-store-readiness
Skill0 starsChanged 3 months agoMITView on GitHub
App Store submission readiness checklist covering privacy manifests, export compliance, permission usage descriptions, App Tracking Transparency, Sign in with Apple parity, and common rejection triggers. Use when asked "is this ready to submit", "will this get rejected", or to check App Store compliance before release.
In this repository10 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If present, check it against actual code:
- Very specific: line 30
If no PrivacyInfo.xcprivacy exists and the app uses any required-reason API or third-party SDKs that collect data, flag this as a …
- Very specific: line 71
If the app uses IDFA or any tracking-adjacent API, it needs NSUserTrackingUsageDescription and must show the ATT prompt …
- Distinctive: line 83
If the app offers a third-party social login (Google, Facebook, etc.) as a primary sign-in option, Apple requires offering Sign in with …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
iOS App Store Readiness
A pre-submission audit, not a guarantee — Apple's actual review process has human judgment calls this can't predict. This procedure catches the mechanical, code-visible reasons apps get rejected or delayed.
1. Privacy manifest
find . -name "PrivacyInfo.xcprivacy"If present, check it against actual code:
- Required-reason API usage — APIs Apple requires a declared reason
for (e.g.
UserDefaults, file timestamp APIs, disk-space APIs, system-boot-time APIs) are declared in the manifest if the code actually calls them. - Collected data types — types declared match what the code and its dependencies actually collect, and whether each is linked to the user's identity or used for tracking.
- Third-party SDK manifests — SDKs that ship their own privacy manifest are current; SDKs that collect data but ship none are a gap to flag.
If no PrivacyInfo.xcprivacy exists and the app uses any required-reason
API or third-party SDKs that collect data, flag this as a submission
blocker, not a nice-to-have.
2. Export compliance
grep -rn "ITSAppUsesNonExemptEncryption" **/*.plist 2>/dev/null
grep -rln "CommonCrypto\|CryptoKit\|SecKey" --include="*.swift" .- Standard HTTPS/TLS usage is export-exempt; check whether the app also
implements custom cryptography (
CommonCrypto,CryptoKitbeyond standard TLS, customSecKeyusage) that would need its own export compliance documentation, not just the standard exemption. ITSAppUsesNonExemptEncryptionshould be set to match reality — set tofalsewhen only using standard exempt encryption avoids an unnecessary compliance question at every submission.
3. Permission usage descriptions
grep -o 'NS[A-Za-z]*UsageDescription' **/*.plist 2>/dev/null
grep -rln "AVCaptureDevice\|CLLocationManager\|PHPhotoLibrary\|EventKit\|CNContactStore\|AVAudioSession.*record" --include="*.swift" .Cross-reference: every permission-gated API actually used in code
(camera, location, photos, contacts, calendar, microphone, etc.) needs
a matching NS*UsageDescription string in Info.plist, and that
string should explain why the app needs it, not just restate the
permission name — "This app uses your location" gets rejected far more
often than "Used to show restaurants near you." Flag both a missing
description string and a present-but-generic one.
4. App Tracking Transparency
grep -rln "AppTrackingTransparency\|ATTrackingManager\|AdSupport" --include="*.swift" .
grep "NSUserTrackingUsageDescription" **/*.plist 2>/dev/nullIf the app uses IDFA or any tracking-adjacent API, it needs
NSUserTrackingUsageDescription and must show the ATT prompt
(ATTrackingManager.requestTrackingAuthorization) before tracking
actually begins, not after.
5. Sign in with Apple parity
grep -rln "GIDSignIn\|FBSDKLoginKit\|GoogleSignIn" --include="*.swift" .
grep -rln "ASAuthorizationAppleIDProvider\|SignInWithAppleButton" --include="*.swift" .If the app offers a third-party social login (Google, Facebook, etc.) as a primary sign-in option, Apple requires offering Sign in with Apple as an equivalent option. This is one of the most common non-obvious rejection reasons — flag it explicitly if a third-party login is found without a corresponding Sign in with Apple implementation.
6. Unused entitlements & background modes
find . -name "*.entitlements" -exec cat {} \;
grep -A10 "UIBackgroundModes" **/*.plist 2>/dev/nullA requested capability or background mode with no corresponding code
usage is both an unnecessary rejection risk and unnecessary attack
surface (see ios-security-review for the security angle on this same
check — don't duplicate that audit here, just flag the App Store risk).
7. Common code-level rejection triggers
- Placeholder or "Lorem ipsum" text/images left in shipped UI.
- Obvious crash-on-launch conditions (force-unwraps on data that could be missing at first launch, e.g. a nil server response).
- Broken or
http://-only links to external content (also flagged inios-security-review's transport-security check). - Any in-app purchase or subscription code that doesn't go through StoreKit (App Store rules require IAP for digital goods/services).
Reporting
Close with the ios-evidence-reporting skill's status block (e.g.
PRIVACY-MANIFEST, EXPORT-COMPLIANCE, PERMISSIONS, ATT,
SIGN-IN-PARITY, ENTITLEMENTS) — only categories actually relevant to
what was reviewed, each backed by the file:line evidence or command
output already shown above. This is a code-visible audit only —
metadata, screenshots, and app description content need a human's
review in App Store Connect and are out of scope here.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

