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
Comments
Are you up for submitting a PR? |
In the Apple forums, as indicated by a DTS engineer, it is recommended not adding an empty privacy manifest for no reason. |
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.🤦♂️ |
@wtmoose do you intend to merge the above mentioned PR? |
@mobru no. Did you read through the comments? I don’t see any case for adding it |
@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. |
@muruganandham I have no idea what “+1” means in the context of this conversation. Could you elaborate? |
FWIW this is the best explanation of the rules that we have found in the Apple documentation so far:
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. |
@jznadams! Yeah we don’t need one |
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.
The text was updated successfully, but these errors were encountered: