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

Apple Privacy Manifest and Signing. #182

Open
JLLA113 opened this issue Feb 1, 2024 · 2 comments
Open

Apple Privacy Manifest and Signing. #182

JLLA113 opened this issue Feb 1, 2024 · 2 comments

Comments

@JLLA113
Copy link

JLLA113 commented Feb 1, 2024

Hi,

Here with a possible issue or doubt.

Related to the Privacy Manifest I see that version 21.0.0 supports Privacy Manifest, but also Apple says that is mandatory to sign the sdk by the developer.

"Signatures are also required when the SDK is used as a binary dependency. This functionality is a step forward for all apps, and we encourage all SDKs to adopt it to better support the apps that depend on them."

Is it planned to integrate that?

Reference:
https://developer.apple.com/news/?id=r1henawx

Thanks

@evgenyneu
Copy link
Owner

If signing is required then yes. Anyone knows how to sign a library?

@ChrisMarshallNY
Copy link

I don't think that you should sign, unless you are delivering a binary (usually in releases). The binary can be signed in the usual way. I believe that most open-source projects do this anyway.

Otherwise, the Git tags and commit hashes can provide a pretty good signing. I think that it may be possible to do more intense tags, but I've never bothered.

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