Invalid values in privacy manifest file

[vlvs]

The values associated with the NSPrivacyCollectedDataTypePurposes keys in the PrivacyInfo.xcprivacy file are invalid.

Rather than the App functionality string currently used as a value of the data types collected by AppSpector, the value string should be NSPrivacyCollectedDataTypePurposeAppFunctionality, as documented at the end of the Describing data use in privacy manifests article.

[deszip]

Hi @vlvs , thanks for pointing this out. Will be fixed in upcoming release.

[tudorgk]

@deszip Because of this, we are also having issues submitting our apps to the App Store. Do you guys have a timeline for the next release? Thank you.

[deszip]

Hi @tudorgk, you use v1.4.11 right? Can you pls show email you got from App Store Connect? Did they mentioned exact key in manifest?

[tudorgk]

Yes, of course!

This is for tvOS:

ITMS-91056: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid: “Frameworks/AppSpectorTVSDK.framework/PrivacyInfo.xcprivacy”. Keys and values in any privacy manifest must be in a valid format. For more details about privacy manifest files, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files.

And this is for iOS:

ITMS-91056: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid: “Frameworks/AppSpectorSDK.framework/PrivacyInfo.xcprivacy”. Keys and values in any privacy manifest must be in a valid format. For more details about privacy manifest files, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files.

[tudorgk]

@vlvs suggestion should fix the issue. @deszip you can try regenerating the manifest by using this link https://www.privacymanifest.dev

[deszip]

We released 1.4.12 version of the sdk with fix. Our test build passed TF checks. Closing this, feel free to reopen in case you still have issues.