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.
Why?
Apps and third-party SDKs should contain a privacy manifest file by Spring 2024 to avoid the app review rejection.
How?
Since swift-user-defaults uses UserDefaults,
NSPrivacyAccessedAPICategoryUserDefaults
C56D.1
?What I'd like you to review/discuss
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api#4278401
I thought
C56D.1
was appropriate as this library provided wrapper functions around UserDefaults API and added some Swift friendly functionalities.But according to this statement, we can't use it since it's exclusively a UserDefaults API wrapper? 😕
However, if
C56D.1
cannot be used, which one would be appropriate for this library? (I don't think any of the options are suitable for our use...)