-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
ITMS-91108: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid: “Frameworks/TOCropViewController.framework/TOCropViewControllerBundle.bundle/PrivacyInfo.xcprivacy”. #595
Comments
I had the same issue too. Checkout the resource by SPM, and saw the structure of PrivacyInfo.xcprivacy is not correct:
it should be:
|
It looks like this was fixed in 2.7.3 https://github.com/TimOliver/TOCropViewController/releases/tag/2.7.3 |
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) |
Hi @TimOliver any news ? |
Same error as @aureliendelrue |
Any update? |
It works! Thanks for the advice. |
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. |
@TimOliver |
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. |
Hello @TimOliver 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 ???? |
Same problem here |
Hi folks! I'm so sorry for the delay! I don't get a lot of free time for open source work these days, but hopefully I can be around a bit more in 2025. It's been a very chaotic year for me trying to support privacy manifests. Over on IGListKit, we decided that privacy manifests shouldn't be necessary since Apple's implied that only these third party SDKs are required to supply their own manifests. A big challenge of this particular issue is it's very hard for me to work out if the privacy manifest was even working or not. 2.7.4 was the second attempt at fixing privacy manifest build errors, and so I needed someone to actually confirm in their own builds if it was working or not. Thanks to those in here who confirmed it for me. 2.7.4 was already pushed on CocoaPods and Carthage, so I'm still not 100% sure what the calls to 'release 2.7.4' were specifically regarding. I've just marked 2.7.4 as the latest release in GitHub. Is that all that was needed? Let me know! Thanks! |
Hello @TimOliver DKImagePickerController I have NO idea whose third party SDK from this list above uses TOcropViewController. EDIT : I have found the solution to target TOCropViewController 2.7.4 don't forget to save file. Now run these commands
in ios directory : Control in Xcode that there is no problem by right-clic on the generated archive and select "privacy report". |
|
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,
The text was updated successfully, but these errors were encountered: