-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ask for the "PrivacyInfo.xcprivacy" required by Apple #103691
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov |
/cc @ivanpovazan |
Hello @baihao,
|
Closing as dup of xamarin/xamarin-macios#20059 |
Hello @ivanpovazan,
Yes, we just want to know the data collection of this library, for macOS, the required reasons APIs are not needed.
Actually No, our product just want to follow Apple's guidelines to provide the privacy manifest, but we do not know these info for third party libraries Thanks a lot for your answer. |
Hi @agocke
It seems it is for |
The title of the repo is now .NET for iOS, Mac Catalyst, macOS, tvOS. It's a part of .NET SDK if I'm correct. |
As far as I know, at this stage we did not investigate how data collection is affected. If you have any concerns could you please post the question in xamarin/xamarin-macios#20059 ?
This blog post includes guidance and information on what are the developer responsibilities when using our frameworks with a detailed list of affected required reason APIs.
It is implicitly applied to dotnet runtime if your app is using our frameworks for Apple platforms. The privacy manifest is imposed by Apple and is needed for all applications published to the App store no matter the version of frameworks or third party libraries/SDKs your application is using. |
Hi team,
Is there a plan to include the
PrivacyInfo.xcprivacy
manifest as required by Apple?ref: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files. Thanks
Dotnet already included the manifest for iOS, iPadOS, and tvOS platforms, but macOS is excluded now.
Regards,
Hao
The text was updated successfully, but these errors were encountered: