Ziparchive Privacy manifest keys are not reflecting in Project privacy report about ziparchive

[rinkusadhwani]

Hi Team, We have release planned in next few days and this issue should be fixed before that otherwise apple will reject the application

Most of the third party sdks showing keys properly in privacy report but ziparchive not.
Please do the needfull. Thanks

[reflectiveworks]

Seeing the same thing in my project on latest ZipArchive. I can see the manifest file in the package but it's still causing:

"ITMS-91053: Missing API declaration - Your app’s code in the “Monolog” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryFileTimestamp. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api."

[Coeur]

It was done 6 months ago already:
#688

And properly released:
https://github.com/ZipArchive/ZipArchive/releases/tag/2.5.5

If there is a bug in the implementation that is only affecting you but not others, then try to figure it out and code a pull request for it.

[rinkusadhwani]

Hi, I am already using the latest version of it. Everything is working fine but ziparchive keys are not reflecting in project privacy report. Thanks, Rinku

…

On Fri, 5 Apr, 2024, 7:57 pm Cœur, ***@***.***> wrote: It was done 6 months ago already: #688 <#688> And properly released: https://github.com/ZipArchive/ZipArchive/releases/tag/2.5.5 If there is a bug in the implementation that is only affecting you but not others, then try to figure it out and code a pull request for it. — Reply to this email directly, view it on GitHub <#698 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXL63YEFRLV3PMEI4XBLH3Y32YDZAVCNFSM6AAAAABE5V2OTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZZHE2DEOBXGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[angusryer]

@rinkusadhwani I'm experiencing something similar, but for me it is related to this issue in react-native-code-push