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

Missing API declaration for NSPrivacyAccessedAPICategoryFileTimestamp #126

Closed
alekkova opened this issue Apr 16, 2024 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@alekkova
Copy link

Describe the bug

When submitting app binary for review we receive an automated warning from Apple:

ITMS-91053: Missing API declaration - Your app’s code in the “App” 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.

AmplifyUILiveness depends on https://github.com/aws-amplify/amplify-swift version 2.27.2, which does not declare the usage for NSPrivacyAccessedAPICategoryFileTimestamp. This has been fixed in 2.27.3 -> https://github.com/aws-amplify/amplify-swift/releases/tag/2.27.3 . Please update the dependency.

Steps To Reproduce

Steps to reproduce the behavior:
1. Submit app binary for Apple review.
2. Receive automated warning from Apple.

Expected behavior

No warning from Apple.

Swift Liveness Version

1.2.9

Xcode version

15.2

Relevant log output

No response

Is this a regression?

No

Regression additional context

No response

OS Version

iOS 17

Device

iPhone 15

Specific to simulators

No response

Additional context

No response

@phantumcode phantumcode added the bug Something isn't working label Apr 17, 2024
@phantumcode
Copy link
Contributor

@alekkova Thanks for submitting the issue. We'll triage the issue and provide updates here.

@phantumcode
Copy link
Contributor

Updates available in version 1.2.10

Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants