feat(ios): Resource Bundle to provide the Privacy Manifest #516
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.
No data is collected in accordance to Apple's definition of collected data.
https://developer.apple.com/app-store/app-privacy-details/#data-collection
“Collect” refers to transmitting data off the device in a way that allows you and/or your third-party partners to access it for a period longer than what is necessary to service the transmitted request in real time.
There is one API that requires a declared reason to use, the NSUserDefaults API. The code is in the base Diagnostic utility class so it's available/used regardless of modules instead, but the actual execution path is only ever invoked through the Motion module.
It uses the standard user defaults object which is private to the application. CA92.1 appears to the best reason description, which describes that the SDK reads and writes information that is only accessible by the app itself and not to other apps or processes.
PR Type
What kind of change does this PR introduce?
What is the purpose of this PR?
Adds a resource bundle which contains a privacy manifest declaring required parameters for this plugin. This in itself is not a breaking change, but does require XCode 15 to use. Older XCode versions will simply ignore privacy manifest files.
No actual code changes have been made.
Does this PR introduce a breaking change?
What testing has been done on the changes in the PR?
This pattern has been tested on several other apache plugins, including the device plugin and file plugin.
What testing has been done on existing functionality?
Other information
CA92.1
is a Apple code which stands for: