1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Thank you for reaching out to us regarding the above query.
For troubleshooting the error, you could check or refer to the below points :
- Confirm if you are logging the error while creating the FaceLiveness session :
<FaceLivenessDetector
sessionId={createLivenessApiData.sessionId}
region="us-east-1"
onAnalysisComplete={handleAnalysisComplete}
onError={(error) => {
console.error(error);
}}
/>
- And, you can refer to the error states mentioned in the below documentation : https://ui.docs.amplify.aws/react/connected-components/liveness#livenesserrorstate
- The initial API call made to Rekognition is the StartFaceLivenessSession API call, hence, you can check the network requests being made or the CloudTrail events to check the request. You may refer to the StartFaceLivenessSession API documentation to see the required parameters for the API.
- StartFaceLivenessSession - https://docs.aws.amazon.com/rekognition/latest/APIReference/API_rekognitionstreaming_StartFaceLivenessSession.html
- Similarly, analyse the Network requests to identify any other failed request and compare the parameters which are passed for the API with the required ones
- You can also refer to the below documentation which discusses the steps in detailed on how to detect real users with aws amplify and face liveness : [+]. https://aws.amazon.com/blogs/mobile/detect-real-users-with-aws-amplify-and-face-liveness/
Having said that, in case you face further challenges, please feel free to open a support case with AWS using the following link.
Contenus pertinents
- demandé il y a un an
- demandé il y a 8 mois
- demandé il y a 4 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 mois