Apple's Privacy Manifests one year in — what's still missing

Required since spring 2024, Privacy Manifests are now non-negotiable for every iOS app submission. A year-plus into the requirement, the same five SDKs are still producing the most rejected submissions.

Privacy Manifests — Apple's PrivacyInfo.xcprivacy requirement for third-party SDKs declaring the data they collect — have been mandatory for every iOS App Store submission since spring 2024. More than a year in, the system has settled, but rejections tied to manifest issues continue at a steady rate.

Where the rejections actually come from

The same five SDK categories show up repeatedly in App Review correspondence: (1) older versions of Firebase (the SDK ships manifests now, but apps pinned to pre-10.x versions don't inherit them), (2) Facebook/Meta SDK if you're using outdated wrapper packages, (3) analytics SDKs from acquired companies (Mixpanel, Amplitude post-acquisition), (4) ad-network SDKs, especially mediation layers, (5) custom internal SDKs your team forgot to manifest.

The cost of getting it wrong

App Review now consistently rejects submissions where the declared data-collection in PrivacyInfo.xcprivacy doesn't match what Apple's static analysis sees in the binary. The fix usually requires one extra submission cycle (1–3 days), but if you're pushing a feature release on a deadline, it's a week of slip.

What to audit

Before every release, run two checks: (a) Xcode's built-in privacy-report generator on the archive, which surfaces missing manifests from linked frameworks; (b) the App Store Connect 'Privacy Details' wizard, which compares your declared collection against what the binary actually does. Mismatches there are the leading cause of rejections in 2026.

What this means for app builders

If you're using SDKs that haven't shipped a manifest update in the last 6 months, replace or upgrade them. The cost of one rejected release is higher than the cost of switching an outdated analytics SDK. Privacy Manifests are settled policy now — Apple isn't walking it back.