Closed qazwsx521943 closed 1 month ago
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?
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:
Closing due to inactivity.
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.
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
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
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.