Privacy Manifest rejects look like mystery ITMS errors

PrivacyInfo.xcprivacy and required-reason APIs are now part of keeping a listing uploadable.

The first time a Privacy Manifest fails, it rarely arrives as a sentence a founder can use. It arrives as an ITMS rejection, a missing PrivacyInfo.xcprivacy, or a third-party SDK that still touches a required-reason API without declaring it.

This is not a product feature. It is platform tax. It also does not care that the app “only shows a map.”

What to check

  • Whether the app target actually ships a manifest
  • Whether SPM and CocoaPods dependencies declare what they access
  • Old analytics and crash SDKs that predate the rules
  • Nutrition labels in App Store Connect that no longer match the binary

If you last opened the project before manifests were mandatory, assume this is on the backlog until someone proves otherwise.

tag: Privacy, App Store