Open KunJeongPark opened 1 month ago
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. I have followed closely your discussions around workarounds for Xcode 15.3 SPM validation error.
Thank you for that as well. We have implemented that workaround and thought Cocoapods could provide a fix for this issue for surfacing static frameworks' privacy terms.
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