ITMS-91108: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid: “Frameworks/TOCropViewController.framework/TOCropViewControllerBundle.bundle/PrivacyInfo.xcprivacy”.

[devender3110]

The PrivacyInfo.xcprivacy file from the following path is invalid: “Frameworks/TOCropViewController.framework/TOCropViewControllerBundle.bundle/PrivacyInfo.xcprivacy”. In addition to the privacy manifest files in the locations outlined in the documentation, starting November 12, 2024, all privacy manifests you submit must have valid content. Keys and values in any privacy manifest must be in a valid format. For more details about privacy manifest files,

[billylongta]

I had the same issue too. Checkout the resource by SPM, and saw the structure of PrivacyInfo.xcprivacy is not correct:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyTracking</key>
	<false/>
	<key>NSPrivacyTrackingDomains</key>
	<array/>
	<key>NSPrivacyCollectedDataTypes</key>
	<array/>
	<key>NSPrivacyAccessedAPITypes</key>
	<array>
		<dict/>
	</array>
</dict>
</plist>

it should be:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyTracking</key>
	<false/>
	<key>NSPrivacyTrackingDomains</key>
	<array/>
	<key>NSPrivacyCollectedDataTypes</key>
	<array/>
	<key>NSPrivacyAccessedAPITypes</key>
	<array/>
</dict>
</plist>

[chrishoffman]

It looks like this was fixed in 2.7.3 https://github.com/TimOliver/TOCropViewController/releases/tag/2.7.3

[aureliendelrue]

I also have this error with 2.7.3 today. @TimOliver could you take a look please ? This file should be in a Sources repository no ? (https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/adding_a_privacy_manifest_to_your_app_or_third-party_sdk#4336749)

[aureliendelrue]

Hi @TimOliver any news ?

[Pbarth]

Same error as @aureliendelrue

[krloz5028]

Any update?

[lgc1993-CN]

I had the same issue too. Checkout the resource by SPM, and saw the structure of PrivacyInfo.xcprivacy is not correct:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyTracking</key>
	<false/>
	<key>NSPrivacyTrackingDomains</key>
	<array/>
	<key>NSPrivacyCollectedDataTypes</key>
	<array/>
	<key>NSPrivacyAccessedAPITypes</key>
	<array>
		<dict/>
	</array>
</dict>
</plist>

it should be:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyTracking</key>
	<false/>
	<key>NSPrivacyTrackingDomains</key>
	<array/>
	<key>NSPrivacyCollectedDataTypes</key>
	<array/>
	<key>NSPrivacyAccessedAPITypes</key>
	<array/>
</dict>
</plist>

It works! Thanks for the advice.
Now, I'm just waiting for version 2.7.4 to merge it.

[aleksandar-vostic]

Any ideas when will 2.7.4 with the fix be?

EDIT: Okay, I just targeted the last commit on the main branch, and it passes Apple's review now.

[lgc1993-CN]

@TimOliver
I saw that v2.7.4 has been tagged. Will it be released soon?

[praveenraman]

https://stackoverflow.com/questions/79221883/itms-91056-invalid-privacy-manifest/79228978#79228978

[JunkyTang]

I also encountered this issue. After upgrading from 2.7.2 to 2.7.3 and submitting again for review, the problem still persists!

[lgc1993-CN]

I also encountered this issue. After upgrading from 2.7.2 to 2.7.3 and submitting again for review, the problem still persists!

You should update to version 2.7.4, which has been tagged in this repository but has not yet been officially released.

[deacon78]

Hello @TimOliver
I don't even know from what third party package TOCropViewController is a dependency...
So I cannot aim your git to update to 2.7.4.

My Apple submission cannot be accepted until you release this version 2.7.4 OFFICIALLY/

I imagine I'm not the only one affected by this bug.

Why don't you simply fix that simple bug and RELEASE that 2.7.4 ????