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
Following definition of "third-party SDKs" that as mentioned in the WWDC23. and according to Privacy manifest files | Apple Developer Documentation, I think this library may also require a Privacy Manifest for the upcoming app review in Spring 2024.
Do you have any plans to add a Privacy Manifest or to have a claim that this library actually does not need a Privacy Manifest?
Thank you very much!
The text was updated successfully, but these errors were encountered:
thank you for raising the topic. 👍🏻 It is a great addition, both signed SPM frameworks and Privacy manifest requirement that Apple introduced.
Sourcery can be used as an SPM package and its code can be used in production in apps which generate Swift code "on the fly". Such as "Sourcery Pro" app, for example.
My personal opinion: better to have it rather than avoid adding a simple file.
But, generally speaking, Sourcery is a tool which mostly used in pre-build phase, for generating Swift source code. It means that it is not supposed to be distributed alongside the final ipa or app distributed to the enduser.
Yeah, what @art-divin said. Zero concern with Sourcery since it's not anything that would ever interact with user data, and 99% of use cases are in pre build, but adding manifest would be fine
Following definition of "third-party SDKs" that as mentioned in the WWDC23. and according to Privacy manifest files | Apple Developer Documentation, I think this library may also require a Privacy Manifest for the upcoming app review in Spring 2024.
Do you have any plans to add a Privacy Manifest or to have a claim that this library actually does not need a Privacy Manifest?
Thank you very much!
The text was updated successfully, but these errors were encountered: