Closed 0xpablo closed 7 months ago
which is weird to me as this is how Xcode create that file when add new one
<?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>NSPrivacyAccessedAPITypes</key>
<array>
<dict/>
</array>
</dict>
</plist>
which is weird to me as this is how Xcode create that file when add new one
Surprised and not surprised at the same time 😂. Maybe it's worth opening a bug report so that they fix their server side checks or their blank template, whichever one is wrong.
Another alternative is that they simply not allow empty manifest although I'm not sure about that.
Thanks for the quick reply!
they do allow empty, and quick googling reveal to me that it is most likely the dict/ that they don't like. the documentation is so much not helpful for the file format
fixed on the main branch 308e1db0592935fe46d3520c55e4d884d5accaa5. to be released soon.
Fixed in 3.1.5001 (allegedly)
Hi there, after updating OpensSSL to the latest version (3.1.5000) via SPM, we received an iTunes Connect warning about the manifest being invalid:
I noticed that the current manifest looks like this:
Looking at other OSS empty manifests, they omit the inner dictionary inside the
NSPrivacyAccessedAPITypes
array, like this:I haven't yet uploaded a build with another 3rd party framework with an empty manifest so I cannot say that will work for sure, but the current manifest is invalid.
Thanks in advance!