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
Comments
This repo's
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.
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: