Subject: Video SDK UI Toolkit iOS — ZoomVideoSDKUIToolkit.framework PrivacyInfo.xcprivacy missing NSPrivacyCollectedDataTypes
Hello Zoom Developer Support,
We are reporting a defect in the privacy manifest shipped inside ZoomVideoSDKUIToolkit.framework in the iOS Video SDK UI Toolkit.
Environment
- Package: GitHub - zoom/videosdk-ui-toolkit-ios: The Zoom Video SDK UI toolkit is a prebuilt video chat user interface powered by the Zoom Video SDK. · GitHub (Swift Package Manager)
- Branch/commit: main @ 6d62fa29 (per your documentation’s recommendation to track main)
- Xcode: [version]
- Deployment target: iOS 15.0+
- Integration: SPM, all four xcframeworks (ZoomVideoSDK, ZoomVideoSDKUIToolkit, zoomcml, CptShare)
Issue
When generating a privacy report from a Production archive (Xcode Organizer → Generate Privacy Report), the report’s “Errors Encountered” section contains:
Missing an expected key: 'NSPrivacyCollectedDataTypes'
LeadMobile.app/Frameworks/ZoomVideoSDKUIToolkit.framework/PrivacyInfo.xcprivacy
On inspection, that manifest contains only NSPrivacyAccessedAPITypes. It is missing NSPrivacyCollectedDataTypes, NSPrivacyTracking, and NSPrivacyTrackingDomains. Xcode’s report generator requires all four top-level keys and fails the file structurally, so the error appears on every archive.
The other three frameworks in the same package are unaffected — ZoomVideoSDK.framework, zoomcml.framework, and CptShare.framework each ship a complete manifest declaring an identical 13-type set (all Linked=YES, Tracking=NO), and all three aggregate into the report correctly. Only the UI Toolkit framework’s manifest is incomplete.
Why we are raising it
Your documentation at Video SDK UI Toolkit - Video SDK - Zoom Developer Docs states that versions 1.11.0-1 and later follow Apple’s requirement to provide a privacy manifest and signatures, linking to Apple’s third-party SDK requirements page. The shipped manifest does not satisfy the structural requirement Xcode enforces, so the documented claim and the observed behaviour do not match.
This also cannot be worked around cleanly at our end. Because the SPM main branch delivers all four xcframeworks as a single package, we cannot remove ZoomVideoSDKUIToolkit.framework without also losing ZoomVideoSDK, zoomcml, and CptShare, which our app depends on. We do not use the UI Toolkit’s views at all — our UI is SwiftUI, which the UI Toolkit does not support — so the framework is embedded solely as a consequence of the package layout.
What we are asking
- Please add the three missing top-level keys to ZoomVideoSDKUIToolkit.framework/PrivacyInfo.xcprivacy. If the UI Toolkit collects nothing beyond what the core SDK already declares, an empty NSPrivacyCollectedDataTypes array with NSPrivacyTracking set to false would resolve the report error.
- Please confirm which release will carry the fix, so we can plan our upgrade.
- Separately: is there a supported way to consume the core Video SDK via SPM without the UI Toolkit framework? The CocoaPods integration exposes per-framework subspecs, but the SPM package appears to be all-or-nothing. A separate SPM product for the core SDK would let apps that build their own UI avoid embedding the toolkit entirely.
One clarification for context, not a complaint: we understand the Video SDK is not on Apple’s list of commonly used third-party SDKs, so Apple does not require you to ship a privacy manifest at all, and this error does not block our App Store upload. Because you do ship one and document it as compliant, an incomplete file produces a persistent error in every customer’s privacy report and makes it harder to answer the App Store Connect App Privacy questionnaire accurately.
Happy to supply the full privacy report PDF, the raw manifest contents, or a minimal reproduction project on request.
Thank you,