Embedding a Privacy Manifest Into an XCFramework
I expected documentation at least, and was hoping for an update in Xcode – specifically the
xcodebuildcommand – to add an option that accepted a path to a manifest and included it appropriately. So far, nothing from Apple on that front. […] I hope that something is planned to make this easier, or at the minimum document a process, since it now appears to be an active requirement for new apps presented to the App Store.[…]
In the meantime, if you’re Creating an XCFramework and trying to figure out how to comply with Apple’s requests for embedded privacy manifests, hopefully this article helps you get there. As I mentioned at the top of this post, this is based on my open source work in Automerge-swift. I’m including the library and XCFramework (and show it off) in a demo application. I just finished working through the process of getting the archives validated and pushed to App Store Connect (with macOS and iOS deliverables). To be very clear, the person I worked with at DTS was both critical and super-helpful. Without this information I would have been wandering blindly for months trying to get this sorted.
Previously:
Update (2024-04-24): Marcin Krzyzanowski:
apple: you have to add a privacy manifest
me: what’s that
apple: it’s a manifest
me: is it a plist file?
apple: use Xcode to make one
me: using Xcode
apple: not like that. The manifest file is invalid
me: what is valid
apple: check documentation
me: it doesn’t say the actual file format
apple: it’s invalid
me: google around and find out what is invalid in plist file because apparently, everyone struggles
