Fixes #23494

Should we treat it as a bug fix and add it on all branches?

Or documentation actually.

As @fwh-dc is the community maintainer of iOS platforms I kindly ask him to review this.

LGTM.

I have one minor thing to consider:
Should we copy this file to the install location of ios build targets to make it more convenient when packaging an xcframework?

There is also a discussion about this at #23262

someone with better knowledge of the config/perl would need to add it to the install process.. At least this gives a reference file.

@fwh-dc Which directory it should be installed to? The same where the libcrypto/libssl .dylib is installed to? BTW the iOS targets by default disable shared build so there is actually no .dylib built. So I would skip installing this anywhere for now.

The iOS targets really need some fine-tuning/cleanups IMO to be more comprehensive and useful.

@fwh-dc Which directory it should be installed to? The same where the libcrypto/libssl .dylib is installed to? BTW the iOS targets by default disable shared build so there is actually no .dylib built. So I would skip installing this anywhere for now.

Good question. I think it's fine to just have the file for reference as suggested. We can always improve from there.

Doesn't this need to be added to the appropriate directory in the podspec and packaging (resource bundle) ?

Based on #23494 (comment), I take it this was derived from the BoringSSL one? Keep in mind that stat appears in this list:
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api?language=objc

We have an empty one, but we'd also removed our remaining stat call. I haven't looked too carefully at this, but it's possible you all may need either code changes or a different manifest.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually.

I do not see a need for us to install this. It's useful documentation for folks building for Apple products.
This is very unlikely to stand by itself as the only things an application needs.

Based on #23494 (comment), I take it this was derived from the BoringSSL one? Keep in mind that stat appears in this list: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api?language=objc

We have an empty one, but we'd also removed our remaining stat call. I haven't looked too carefully at this, but it's possible you all may need either code changes or a different manifest.

Yeah maybe we need to declare C617.1 Although we never use the timestamp info obtained with stat.

OTC: We are OK with adding the file. The contents need to be right. It seems we need to declare C617.

C617 is probably not right, and we might need to ask apple for a new id.

Any reason why C617 is not right?

Is there someone who actually has Xcode installed who can generate this file
I dont feel comfortable trying to add this entry manually - and I dont have access to Xcode + MAC to do this..

(Submit a new PR if you want)
Basically the NSPrivacyAccessedAPITypes section needs
NSPrivacyAccessedAPIType=APICategoryFileTimeStamp
NSPrivacyAccessedAPITypeReasons=C617.1

In light of #24260 can this be closed now?

I would think so.