Privacy manifest file for iOS is missing

[Jjagg]

Hi!

Please consider adding a privacy manifest to your library. This helps developers reflect data collection practices in our own manifests. All iOS packages should include a privacy manifest.

Apple documentation.

First-party example: flutter/packages#5846

I did a quick check and AFAICT there's nothing you need to put in there for this package, so you can use the following manifest:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyTrackingDomains</key>
	<array/>
	<key>NSPrivacyAccessedAPITypes</key>
	<array/>
	<key>NSPrivacyCollectedDataTypes</key>
	<array/>
	<key>NSPrivacyTracking</key>
	<false/>
</dict>
</plist>

[matszafraniec]

Hello @Jjagg . Thank you for notifying me in this topic.

I checked this subject and in codebase I can't find references to the API covered in Apple documentation. So in my opinion this package is not affected by this change.

[Jjagg]

Hi @matszafraniec. Yes, a privacy manifest is not required at this time. I'll note that Apple in their initial enforcement from May 1st on is already requiring privacy manifests for popular packages, even if they do not use required reason APIs.
Because of this, the Flutter team has added a privacy manifest to all first-party packages, even though most of them are empty: fluttercommunity/plus_plugins#2447.

Additionally an empty privacy manifest can confirm to users that this package has considered adding a privacy manifest and does not use any required reason APIs.

Feel free to close this issue and the PR if you prefer not to add a privacy manifest at this time. People that depend on this package can find this issue to know that this package does not need a privacy manifest.
If Apple ever requires a manifest for all packages or enforcement would otherwise include this package, the PR is there and can be reopened :)

[matszafraniec]

@Jjagg Thank you for exhaustive response and support. Yes, I see that some packages add this privacy manifest in advance, even if they're not using required APIs. My recommendation is to keep an eye one it and if anyone face this issue, I can update the package but as long as it is not required let's do not add it.

[matszafraniec]

I leave this topic as open for some time.