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

Invalid Privacy Manifest warning when uploaded to App Store #198

Closed
james-wag opened this issue Mar 25, 2024 · 5 comments
Closed

Invalid Privacy Manifest warning when uploaded to App Store #198

james-wag opened this issue Mar 25, 2024 · 5 comments

Comments

@james-wag
Copy link

Any application uploaded to App Store Connect that currently integrates the SDK will get the following warning:

ITMS-91056: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid: "Frameworks/MapboxCommon.framework/PrivacyInfo.xcprivacy". While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, keys and values in your app's privacy manifest must be in a valid format. For more details about privacy manifest files, visit:

It appears that a new privacy manifest file is needed at the MapboxCommon directory level is needed like in the following Apple Doc https://developer.apple.com/documentation/bundleresources/privacy_manifest_files

@dudeuter
Copy link

Hi James,

This is something we're working to address on our end, it'll be addressed before May 1st. (Likely in the next version)

@aokj4ck
Copy link
Contributor

aokj4ck commented Apr 26, 2024

@james-wag which version of the SDK are you using now?

@james-wag
Copy link
Author

@aokj4ck I was using 2.0.0-rc2. I do see that there's been an r3 release since I opened this issue.

@aokj4ck
Copy link
Contributor

aokj4ck commented Apr 26, 2024

@james-wag okay you can try out this branch xcprivacy-searchcore_beta17 (link) which is in pull request review. This should be compatible with Xcode 15.0 to 15.2.

Please let me know if you encounter any issues.

@james-wag
Copy link
Author

Closing in favor of #233 which is more up-to-date with current app store submission issues.

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