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

FaceLiveness.FaceLivenessDetectionError Code 1 #173

Closed
qazwsx521943 opened this issue Sep 4, 2024 · 4 comments
Closed

FaceLiveness.FaceLivenessDetectionError Code 1 #173

qazwsx521943 opened this issue Sep 4, 2024 · 4 comments
Labels
bug Something isn't working investigating This issue is being investigated pending-community-response Issue is pending response from the issue requestor

Comments

@qazwsx521943
Copy link

Describe the bug

We received some user responses mentioning that they cannot go through the liveness test no matter how many times they try. After viewing our remote logs, we found out for some users they encounter the error: The operation couldn’t be completed. (FaceLiveness.FaceLivenessDetectionError error 1.).

Steps To Reproduce

This cannot be reproduced on my device or on our company’s QA devices.
But we are creating a sessionID server side, and passing the session ID to the FaceLivenessDetectorView initializer, and some of the users encounters this error code when we check the remote event logs.

Expected behavior

The FaceLiveness Detector view should start when accepting valid sessionID

Swift Liveness Version

1.3.2

Xcode version

15.2

Relevant log output

The operation couldn’t be completed. (FaceLiveness.FaceLivenessDetectionError error 1.)

Is this a regression?

No

Regression additional context

No response

OS Version

17.5.1

Device

iPhone 11 Pro

Specific to simulators

No response

Additional context

This is intermittent. This happens to some users and we are not sure why.

@github-actions github-actions bot added pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Sep 4, 2024
@5d 5d added the investigating This issue is being investigated label Sep 4, 2024
@5d
Copy link
Member

5d commented Sep 4, 2024

Hi @qazwsx521943 ,

Thank you for bringing this issue to our attention. Our team will investigate to identify any possible causes.
In the meantime, we don’t have an iPhone 11 Pro available for testing. Could you let us know the most recent device model reported by your customers as being affected?

@github-actions github-actions bot removed the pending-maintainer-response Issue is pending response from an Amplify team member label Sep 4, 2024
@thisisabhash
Copy link
Member

Hello, Could you please post the verbose logs from the remote logs? Alternatively, you can print the error received to determine the cause on your side. The error codes are listed here:

https://github.com/aws-amplify/amplify-ui-swift-liveness/blob/main/Sources/FaceLiveness/Views/Liveness/FaceLivenessDetectionError.swift

@thisisabhash thisisabhash added bug Something isn't working and removed pending-triage Issue is pending triage labels Sep 9, 2024
@ruisebas ruisebas added the pending-community-response Issue is pending response from the issue requestor label Sep 12, 2024
@ruisebas
Copy link
Member

Closing due to inactivity.

@ruisebas ruisebas closed this as not planned Won't fix, can't repro, duplicate, stale Sep 30, 2024
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 investigating This issue is being investigated pending-community-response Issue is pending response from the issue requestor
Projects
None yet
Development

No branches or pull requests

4 participants