Open caosuyang opened 6 months ago
To the best of my knowledge, Draco base library is not using any SDKs or third party dependencies so I don't think any action should be necessary on Draco side.
Sorry, my description may have caused you to misunderstand. The Draco base library does not use any SDK or third-party dependencies, but does it use https://developer.apple.com/support/third-party-SDK-requirements/ As for the interface mentioned in it, this is what I pay attention to when using the Draco library. If it is involved, you need to add the PrivacyInfo.xcprivacy privacy manifest file. For more details, see https://developer.apple.com/support/third-party-SDK-requirements/
Description
At the end of April, after the latest version of Apple submitted for review, Apple restored a warning email, which does not block the review at present. According to the official warning, it will be used as a condition for blocking the review around May. We hope to deal with the warning problem before May. According to Apple's May 1 Privacy Policy, if you use the API in your app's code, you need to report the API in the app's privacy manifest file. If you use the API in the code of a third party SDK, you will need to report the API in the privacy manifest file of the third party SDK. Since we use Swift packages to reference the draco framework in our app, but I can't see which interfaces need to handle Apple's privacy policy in the dynamic library, I hope the author can check the interfaces in the implementation code. Then add the PrivacyInfo.xcprivacy file.
Version
v1.5.6
How the app depends on the framework
Swift packages
App Store review issues
Write at the end
We hope to get a clear reply and solution as soon as possible, so that we can deal with the review of Apple's shelves in May. Thank you.