Adds NSPrivacyAccessedAPICategoryUserDefaults to privacy manifest #243
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
winsmith
approved these changes
Apr 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Once we updated one of our apps to the latest version of the SDK, it got rejected by App Store Review for it was missing the
NSPrivacyAccessedAPICategoryUserDefaultsentry in the privacy manifest. We tracked it down to the TelemetryDeck SDK.This PR addresses the issue by adding the missing description to both privacy manifests. Our app was accepted using a fork of the library with this change 🤩 .
Cheers,
K
PS: perhaps a step can be added to the GitHub workflow to check that? e.g. https://github.com/crasowas/app_store_required_privacy_manifest_analyser