You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple recently announced that starting in 2024/5/1, apps will be required to include more privacy-related reasoning for "third-party SDKs." This includes providing details in privacy manifests about data use by these SDKs. You can read more about this requirement on the Apple Developer website: Describing Data Use in Privacy Manifests
Many popular Flutter plugins, such as shared_preferences, have already implemented these manifests. You can see an example of such a manifest in the shared_preferences plugin here: PrivacyInfo.xcprivacy
Given these upcoming requirements, it's important to note that even libraries that do not collect privacy-policy-relevant information may need to include an empty PrivacyInfo.xcprivacy file to avoid potential rejection.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered:
It looks like this package itself does not use native iOS functionality.
My apologies.
But maybe you need to update the package and plugins such as url_launcher that you rely on internally to a version that is compatible with PrivacyInfo.
kazy-dev
changed the title
[iOS] Are there any plans to add Privacy Manifests?
Are there any plans to update dependent packages to Privacy manifest-compliant versions?
Mar 20, 2024
Apple recently announced that starting in 2024/5/1, apps will be required to include more privacy-related reasoning for "third-party SDKs." This includes providing details in privacy manifests about data use by these SDKs. You can read more about this requirement on the Apple Developer website: Describing Data Use in Privacy Manifests
Many popular Flutter plugins, such as shared_preferences, have already implemented these manifests. You can see an example of such a manifest in the shared_preferences plugin here: PrivacyInfo.xcprivacy
Given these upcoming requirements, it's important to note that even libraries that do not collect privacy-policy-relevant information may need to include an empty PrivacyInfo.xcprivacy file to avoid potential rejection.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: