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

Any plan for Privacy Manifest? #1235

Open
Angus-chang opened this issue Dec 7, 2023 · 2 comments
Open

Any plan for Privacy Manifest? #1235

Angus-chang opened this issue Dec 7, 2023 · 2 comments

Comments

@Angus-chang
Copy link

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!

@art-divin
Copy link
Collaborator

Hello @Angus-chang ,

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.

@krzysztofzablocki
Copy link
Owner

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

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

3 participants