Find agent skills by outcome

What Apple checks: The age rating you declare must match the actual content. If a reviewer encounters mature content (violence

sexual themes

Creative

> Remove this sentence. It violates 2.3.3. You also cannot show Android-style UI elements (Material Design bottom sheets

FABs

> This will be rejected under 5.2.2 (misleading metadata). Take real screenshots using the Xcode simulator or a physical device. You may add a colored background

marketing text overlay

> Test on a physical device running iOS 16.0. Common failure modes include: APIs that were added in iOS 17 called without `if #available(iOS 17

*)` guards

> All three are public

documented frameworks. No private API risk here. Run `nm -u YourApp.app/YourApp | grep U ` on your built binary to list all imported symbols and spot anything unexpected.

> This will be caught by automated analysis and rejected before a human reviewer sees it. Replace with the public UIKit animation APIs (`UIViewPropertyAnimator`

`UIView.animate`). Search your dependency tree for known private API wrappers — run `grep -r _UIPrivate\|UIApplication.*openURL .` in your project to surface obvious calls.

Data

> This is acceptable. It names the feature (map)

the data used (location)

> This is likely to be flagged. Apple expects you to explain what the camera is used for in user-facing terms. Replace it with something like: `Used to scan QR codes when checking into venues.` The description must match actual usage — if the reviewer grants permission and sees no camera feature

the app is rejected under 5.1.1.

Be specific. Do not give generic advice. Reference the actual guideline number. If the user provides code or feature details

tailor your response to their actual implementation.

- When giving code fixes

use Swift unless the user specifies otherwise.

Action: [Exact steps to fix or verify

with code snippets or commands where applicable]

> Correct. After archiving

open the generated `.xcarchive` and check `Products/Applications/YourApp.app/PrivacyInfo.xcprivacy` is present. You can also run the privacy report in Xcode Organizer (Window → Organizer → Privacy Rep...

What Apple checks: Since Spring 2024

apps using certain APIs (file system

> You need three things: (1) A `PrivacyInfo.xcprivacy` file in your app target declaring reasons for `NSUserDefaults` access (likely `CA92.1` — user defaults) and `NSFileManagerAPI` (likely `0A2A.1` — app functionality). (2) Verify Firebase SDK version — Firebase 10.18+ includes its own privacy manifest. If you're on an older version

upgrade. (3) In Xcode

What Apple checks: Apple enforces a minimum SDK version after each WWDC cycle. As of 2025

apps must be built with Xcode 15+ targeting iOS 17 SDK minimum. Submitting with an outdated Xcode version is automatically rejected by the upload pipeline before review.

> Migrate the endpoint to HTTPS before submission. If you absolutely cannot (e.g. a third-party API you don't control)

use `NSExceptionDomains` to allowlist only that specific domain instead of disabling ATS globally. You'll still need to justify it in the review notes. Global `NSAllowsArbitraryLoads` without justific...

What Apple checks: The app must render correctly on the latest iPhone screen dimensions

including Dynamic Island devices (iPhone 14 Pro and later). Hardcoded frame sizes

Writing & Content

What Apple checks: The age rating you declare must match the actual content. If a reviewer encounters mature content (violence

sexual themes

Writing & Content

> User-generated content automatically requires a 17+ rating unless you implement moderation. You need: (1) a mechanism to report/flag content

(2) a stated moderation policy in your metadata

Creative

> Remove this sentence. It violates 2.3.3. You also cannot show Android-style UI elements (Material Design bottom sheets

FABs

> This will be rejected under 5.2.2 (misleading metadata). Take real screenshots using the Xcode simulator or a physical device. You may add a colored background

marketing text overlay

> Test on a physical device running iOS 16.0. Common failure modes include: APIs that were added in iOS 17 called without `if #available(iOS 17

*)` guards

> All three are public

documented frameworks. No private API risk here. Run `nm -u YourApp.app/YourApp | grep U ` on your built binary to list all imported symbols and spot anything unexpected.

> This will be caught by automated analysis and rejected before a human reviewer sees it. Replace with the public UIKit animation APIs (`UIViewPropertyAnimator`

`UIView.animate`). Search your dependency tree for known private API wrappers — run `grep -r _UIPrivate\|UIApplication.*openURL .` in your project to surface obvious calls.