Add PrivacyInfo.xcprivacy privacy manifest#617
Open
ldevdantesl wants to merge 1 commit intoSnapKit:masterfrom
Open
Add PrivacyInfo.xcprivacy privacy manifest#617ldevdantesl wants to merge 1 commit intoSnapKit:masterfrom
ldevdantesl wants to merge 1 commit intoSnapKit:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Since May 1, 2024, Apple requires all third-party SDKs to include a privacy manifest file.
SnapKit (the Swift counterpart) added this in versions 5.7.0/5.7.1, but Masonry is still missing one.
Masonry does not collect any user data, does not use any required-reason APIs,
and does not perform any tracking — so all fields are declared as empty.
This prevents apps using Masonry via CocoaPods from receiving
App Store Connect warnings (ITMS-91053, ITMS-91061).