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
Privacy Manifest Not Surfacing for Static Framework in CocoaPods Integration #12365
Comments
This may be an Apple detection issue. Note the dynamic framework wording in https://developer.apple.com/news/?id=pvszzano |
@paulb777 Thank you for your reply and the Apple link. That is interesting that they announced this on Friday. Thank you for that as well. We have implemented that workaround and thought Cocoapods could But I agree that Apple's wording implies that there may be official guidelines regarding static frameworks. |
Report
We have identified an issue where the privacy terms defined in the PrivacyInfo.xcprivacy files of our static framework dependencies are not being surfaced in the privacy report of test apps that integrate our SDK via CocoaPods. This issue specifically affects our
PPRiskMagnes.xcframework
, which is included in ourBraintreeDataCollector
subspec.What did you do?
What did you expect to happen?
The privacy terms specified in the PrivacyInfo.xcprivacy file within the PPRiskMagnes.xcframework should be correctly surfaced in the app’s privacy report, ensuring compliance and transparency.
What happened instead?
The privacy terms are not being surfaced in the app’s privacy report when the SDK is integrated via CocoaPods, despite the inclusion of these terms in the framework’s bundled resources.
CocoaPods Environment
Project that demonstrates the issue
bt_coco_vp.zip
you need to run pod install
The text was updated successfully, but these errors were encountered: