aws-amplify / amplify-ui-swift-liveness

This repository offers a UI component for Amazon Rekognition Face Liveness, enabling developers to ensure that only authentic users, and not bad actors using spoofs, can access their services.
https://ui.docs.amplify.aws/swift/connected-components/liveness
Apache License 2.0
8 stars 18 forks source link

Missing API declaration for NSPrivacyAccessedAPICategoryFileTimestamp #126

Closed alekkova closed 2 months ago

alekkova commented 2 months ago

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 commented 2 months ago

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

phantumcode commented 2 months ago

Updates available in version 1.2.10

github-actions[bot] commented 2 months ago

⚠️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.