Skip to content
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

Replace required reason APIs with equipment Foundations APIs on Apple targets #297

Closed
fzhinkin opened this issue Apr 22, 2024 · 0 comments · Fixed by #298
Closed

Replace required reason APIs with equipment Foundations APIs on Apple targets #297

fzhinkin opened this issue Apr 22, 2024 · 0 comments · Fixed by #298
Assignees

Comments

@fzhinkin
Copy link
Collaborator

Starting from May 1st, 2024, developers have to explicitly describe why they are using some APIs for apps published in AppStore, apps won't be accepted (see this for more info).

One such API is stat, which we use to gather file metadata. It should be replaced with NSFileManager calls.

@fzhinkin fzhinkin self-assigned this Apr 22, 2024
fzhinkin added a commit that referenced this issue Apr 22, 2024
Starting from May 1, 2024 developers have to explicitly
declare why they use APIs allowing to access
file timestamps in a privacy manifest files;
otherwise an app won't be accepted by the AppStore.
The only restricted API we're currently using
is stat, and since we don't extract any timestamps
using it, we can safely replace it with
NSFileManager::fileAttributesAtPath.

For more details on the restriction imposed on
timestamp-accessing APIs read https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api

Closes #297
@fzhinkin fzhinkin linked a pull request Apr 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant