Repository navigation
|
My app was flagged or rejected on App Store for this. Required reason APIs or third party SDKs without a privacy manifest. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Privacy Manifest (App Store) Severity in the playbook. critical What triggers it. Required reason API usage or a commonly used third party SDK is present but no PrivacyInfo.xcprivacy is bundled, or an SDK lacks its signed manifest. Enforced by Apple at upload since 2024. What to search your code for. How to fix it. Add a PrivacyInfo.xcprivacy with NSPrivacyAccessedAPITypes and approved reason codes, list NSPrivacyTrackingDomains, and confirm every third party SDK ships its signed manifest. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Privacy Manifest (App Store)
Severity in the playbook. critical
What triggers it. Required reason API usage or a commonly used third party SDK is present but no PrivacyInfo.xcprivacy is bundled, or an SDK lacks its signed manifest. Enforced by Apple at upload since 2024.
What to search your code for.
NSFileManager,UserDefaults,systemUptime,ProcessInfo,Firebase,AlamofireHow to fix it. Add a PrivacyInfo.xcprivacy with NSPrivacyAccessedAPITypes and approved reason codes, list NSPrivacyTrackingDomains, and confirm every third party SDK ships its signed manifest.
The guard reports this as
APPLE-PRIVACY-MANIFEST-MISSING. The full pattern is in data/rejection-patterns.json.Thi…