CocoaPods Privacy Manifests FAQs

Question 1

Why does my CocoaPods library need a privacy manifest?

Accepted Answer

Apple requires apps and SDKs to provide a PrivacyInfo.xcprivacy file to disclose data usage and the use of 'Required Reasons' APIs starting with iOS 17 to prevent fingerprinting.

Question 2

Can I use different manifests for iOS and macOS within the same pod?

Accepted Answer

Yes, the skill provides specific podspec patterns for platform-specific resource bundles to handle different privacy requirements across iOS and macOS targets.

Question 3

What are Required Reasons APIs?

Accepted Answer

These are specific Apple APIs (like UserDefaults, System Boot Time, or File Timestamps) that require a declared justification code in the privacy manifest to explain why the app needs access.

Question 4

Does this skill handle tracking domains?

Accepted Answer

Yes, it provides templates and best practices for declaring tracking domains and NSPrivacyTracking boolean flags to satisfy App Store transparency rules.

Question 5

How do I include the manifest in my podspec?

Accepted Answer

It is best practice to include it via spec.resource_bundles to ensure the manifest is correctly namespaced and integrated into the consumer's final app bundle without conflicts.

CocoaPods Privacy Manifests

Key Features

Use Cases

CocoaPods Privacy Manifests

Key Features

Use Cases