Skip to content
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

Add Privacy manifests file #546

Closed
yasiraliraj opened this issue Mar 25, 2024 · 11 comments
Closed

Add Privacy manifests file #546

yasiraliraj opened this issue Mar 25, 2024 · 11 comments

Comments

@yasiraliraj
Copy link

Hello Team,

I hope this message finds you well. I would like to draw your attention to an important update required by the App Store. Starting May 1, 2024, a privacy manifest will be mandatory for all apps. Given the ongoing development and support for your SDK, integrating this feature would be highly beneficial for ensuring compliance with the new App Store guidelines. This addition would greatly help developers like us in continuing to provide seamless services through our applications. We appreciate your attention to this matter and look forward to any updates you can provide.

Thank you for your continued support.

@wtmoose
Copy link
Member

wtmoose commented Mar 25, 2024

Are you up for submitting a PR?

@yasiraliraj
Copy link
Author

@wtmoose Please check the PR: #547

@SunZhiC
Copy link

SunZhiC commented Apr 4, 2024

In the Apple forums, as indicated by a DTS engineer, it is recommended not adding an empty privacy manifest for no reason.

@wtmoose
Copy link
Member

wtmoose commented Apr 4, 2024

Interesting. That seems like a bad design. There’s no way to distinguish between a library that doesn’t need a manifest from one that does, but hasn’t added one yet.🤦‍♂️

@mobru
Copy link

mobru commented Apr 15, 2024

@wtmoose do you intend to merge the above mentioned PR?

@wtmoose
Copy link
Member

wtmoose commented Apr 15, 2024

@mobru no. Did you read through the comments? I don’t see any case for adding it

@mobru
Copy link

mobru commented Apr 15, 2024

@wtmoose I did, yeah. But looking a the proposed Privacy Manifest here, it looks like it would not be empty, and therefore required. Or am I misunderstanding something here (and sorry if so)?

@wtmoose
Copy link
Member

wtmoose commented Apr 15, 2024

@mobru my fault. I assumed it was empty and didn't read the file. I don't know where @yasiraliraj came up with those items. I can't think of any reason why the SwiftMessages manifest would not be empty. I'll give @yasiraliraj a chance to justify the changes and then close the PR.

@wtmoose
Copy link
Member

wtmoose commented Apr 25, 2024

@muruganandham I have no idea what “+1” means in the context of this conversation. Could you elaborate?

@jznadams
Copy link

FWIW this is the best explanation of the rules that we have found in the Apple documentation so far:

  • You need to include a privacy manifest file in your third-party SDK if it’s listed in “SDKs that require a privacy manifest and signature,” in Upcoming third-party SDK requirements.
  • Otherwise, include a privacy manifest file in your third-party SDK if it uses required reasons API, collects data about the person using apps that include the third-party SDK, enables the app to collect data about people using the app, or contacts tracking domains.

https://developer.apple.com/documentation/bundleresources/privacy_manifest_files

So sounds to me that if you don't use a required reasons API you don't need a manifest in the library.

@wtmoose
Copy link
Member

wtmoose commented Apr 25, 2024

@jznadams! Yeah we don’t need one

@wtmoose wtmoose closed this as completed May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants