Fix Privacy Manifests, Add To Xcode Targets #3831
Merged
Conversation
This file contains 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
FONickReichard
added a commit
to FONickReichard/Alamofire
that referenced
this pull request
Apr 15, 2024
Moved "PrivacyInfo.xcprivacy" from exclude to the resources array from Alamofire#3831
FONickReichard
added a commit
to FONickReichard/Alamofire
that referenced
this pull request
Apr 15, 2024
…clude to the resources from Alamofire#3831 Moved "PrivacyInfo.xcprivacy" from exclude to the resources from Alamofire#3831
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.
Goals ⚽
The privacy manifest implementation from #3792 was incorrect (thought I had checked it) and breaks the package. This fixes the packages and adds the manifest to the raw framework targets as well.