New privacy manifest

[marianstiehler]

New empty privacy manifest

The previous privacy manifest has been rejected by Apple. I tested it. It fails the automatic checks when submitting a build for review. This was their response:

ITMS-91056: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid:
“StatKit_StatKit.bundle/PrivacyInfo.xcprivacy”. Keys and values in your app’s privacy manifests must be valid. For more
details about privacy manifest files, visit:
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files.

This new privacy manifest gives the same information as far as I can see it: No tracking, nothing. It’s "empty".

This new privacy manifest has been accepted by Apple on Sunday, May 18th 2025. It passed both the automatic and the manual review on Monday.

Please double check this contribution. Perhaps you know more about privacy manifests than I do.

[JimmyMAndersson]

Hi Marian,

Thanks for bringing this to my attention!
It does indeed look like some combinations of elements in the privacy manifest generates an invalid app privacy report. I've experimented by generating reports for a sample application, and it seems like NSPrivacyTracking set to false and an empty NSPrivacyCollectedDataTypes array should do the trick.

I've left a comment on which element to put back into the manifest. Could you verify that it looks correct and submit a change to the PR? I'd be happy to merge it into the project.

[marianstiehler]

I'm not an expert in GitHub (yet). I have modified the pull request, but messed up one commit's description / title. 😉 Sorry.

I have uploaded a new build of my personal app to Apple, and it went through their process. 🙂

[JimmyMAndersson]

Thanks a lot!
I'll get this out into a new patch release in just a minute. :)