breautek commented on issue #1391:
URL: https://github.com/apache/cordova-ios/issues/1391#issuecomment-2090390525

   > And I still received the ITMS-91056: Invalid privacy manifest error. Any 
ideas?
   
   Your manifest looks right to me.
   
   So few things to double check:
   
   1. Cordova-ios@7.1.0 or later is required, that's the version that 
introduces privacy management for the app.
   2. You can double check the `PrivacyInfo.xcprivacy` file in the native 
project to ensure it looks right there.
   3. You can scan for other `PrivacyInfo.xcprivacy` files. Each framework/SDK 
that you import should be providing their own manifest file. Maybe a privacy 
manifest being imported from an SDK is malformed.
   
   When doing your scan, you'll should find at least 2 `PrivacyInfo.xcprivacy` 
files: one that belongs to CordovaLib, which is the privacy manifest for the 
cordova core framework itself. It does not collect or use any priviledged APIs 
that requires declaration so the privacy file is essentially empty, declaring 
it does no tracking, or collects any APIs.
   
   The second privacy manifest file would be your application manifest file, 
that is managed by the `privacy-manifest` tag as you have declared. You'll find 
this at `platforms/ios/<Your App Name>/PrivacyInfo.xcprivacy`
   
   It won't be formatted, but you can copy it into any XML formatter to get it 
pretty-formatted. Your contents should be within:
   
   ```xml
   <?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">
   <!-- contents of your privacy-manifest in here -->
   </plist>
   ```
   
   If you see your contents it there successfully, then I'll start to think 
it's a third-party SDK. They will have their own `PrivacyInfo.xcprivacy` files 
bundled in their `.framework`, .xcprivacy` or sometimes inside a `.bundle` 
files, which are just folders that can expanded and browsed. If it's an issue 
with a third-party SDK, then it would be on them to address it.
   
   If only Apple actually provided us details instead of saying "something is 
wrong, go guess what it is".
   
   You could also try authoring the privacy manifest inside XCode using their 
plist editor (an UI that imo is not very intuitive) and then compare/copy the 
resulting xcprivacy contents into your `privacy-manifest`, just in case there 
is a dumb typo somewhere that neither of us is seeing.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to