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

iOS developer signature #955

Open
markt-bigfish opened this issue Apr 2, 2024 · 3 comments
Open

iOS developer signature #955

markt-bigfish opened this issue Apr 2, 2024 · 3 comments

Comments

@markt-bigfish
Copy link

markt-bigfish commented Apr 2, 2024

I saw this pull request addresses Apple's Privacy Manifest requirement. However, there is an requirement discussed here Upcoming third-party SDK requirements, nanopb is on "the list", about the requirement of developer signatures: "Signatures are also required in these cases where the listed SDKs are used as binary dependencies". We don't use nanopb directly, but I have noticed that Firebase Analytics does use as a dependency. Just curious if this is being addressed or what action we all may have to take.

@PetteriAimonen
Copy link
Member

@ncooke3 @paulb777 Any thoughts?

Also, if anyone can "explain like I'm 5 years old" to me what all this is about, i.e. what is Apple's goal with this and why does it affect nanopb in the first place, I would appreciate it.

@ncooke3
Copy link
Contributor

ncooke3 commented Apr 2, 2024

We don't use nanopb directly, but I have noticed that Firebase Analytics does use as a dependency. Just curious if this is being addressed or what action we all may have to take.

This repo's Package.swift distro distributes nanopb from source for Apple platforms. Firebase manages a source distro of nanopb for CocoaPods and a binary distribution of nanopb for the Zip option. @markt-bigfish, Firebase will be signing the binary distributions to meet the requirements (follow firebase/firebase-ios-sdk#12238).


Also, if anyone can "explain like I'm 5 years old" to me what all this is about, i.e. what is Apple's goal with this...

In June 2023, Apple introduced privacy manifests to standardize privacy practices for the Apple Developer ecosystem in an enforceable, extendable format.

Privacy manifests are property list files that record (a) the type of data collected by a given app or SDK, and (b) the required reasons APIs the given app or SDK uses, and (c) two other fields related to tracking.

...why does it affect nanopb in the first place...

In December 2023, Apple published a list of "commonly used SDKs in apps on the App Store" that require a privacy manifest. Nanopb is on the list.


This bug can be closed because this repo does not release a binary distro of nanopb for Apple platforms.

@markt-bigfish
Copy link
Author

Thank you for clarification @ncooke3. Overall, this Privacy Manifest stuff has been a bit confusing for most. Apple's messaging, and documentation to extent, has been subpar in my opinion.

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