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.
π² What
Updates min version to 7.10.0 up to next major version 7.11.0 (Latest).
π€ Why
Main reference for what's going on
But, Apple requires us to give reasons for using certain APIs. Reasons that need to be added to a Privacy Manifest file (added in that PR βοΈ )
One of the APIs that our app is missing a reason for is
NSPrivacyAccessedAPICategoryFileTimestamp
.We aren't actually using this API internally, Kingfisher is.
Kingfisher added privacy support for Apple's new requirement in 7.10.0. So, by updating the version we're using we should now be meeting the requirement.
π How
set minimum version to 7.10.0 (version that they added privacy support) up to next major version (7.11.0)
π See
Kingfisher's Privacy Manifest which contains the File Timestamp type and reason that Apple is warning us about.
β Acceptance criteria