This document lists the code list and solutions for issues that occur with the liveness detection SDK.
| Code | Description | Solution | Platform |
|---|---|---|---|
| CAMERA_OPEN_FAILED | Failed to open the camera properly. | For Android: Camera opening failed, usually due to the camera being occupied by another process or the current process failing to release the camera. Please check if the app is not correctly releasing the camera resources, or if another process is using the camera. If the problem persists, please check if the camera hardware is unavailable. For iOS: This issue typically occurs when the camera is occupied by another session. Generally, trying again later will resolve it. | Both |
| NO_CAMERA_PERMISSION | The SDK cannot access the camera | Please enable camera permissions in Settings | iOS Only |
| LOAD_JNI_FAILED | Error loading the .so file within the SDK. | Typically, this is due to the missing .so files built into the SDK in the APK installed by the user. If the APK is a debug version, it may be caused by Android Studio's cache; please clear the cache and rerun the project. If this occurs on a real user's phone in a production environment, please confirm with the user that the installed APK version is not from peer sharing, as shared APKs may be incomplete. | Android Only |
| FACE_MISSING | During the detection process, the face disappeared from the camera area. | In certain scenarios of liveness detection, the disappearance of the face is a risk factor, as it may indicate malicious impersonation. We will terminate the detection and return this error code. | Both |
| ACTION_TIMEOUT | Liveness timeout. | Please ask the user to retry and complete the liveness check as required. | |
| MULTIPLE_FACE | During the liveness process, multiple faces were detected. | Similar to face, the presence of multiple faces in certain scenarios of liveness detection is a risk factor, as it may indicate malicious impersonation. We will terminate the detection and return this error code. | Both |
| MUCH_MOTION | The user's motion amplitude is too large. | In certain scenarios of liveness detection, excessive motion amplitude may indicate a higher risk. We will terminate the detection and return this error code. | Both |
| STRONG_LIGHT | The lighting is too strong. | Please ask the user to perform the liveness detection under normal lighting conditions. | Both |
| WEAK_LIGHT | The lighting is too. | Please ask the user to perform the liveness detection under normal lighting conditions. | Both |
| AUTH_PARSE_ERROR | Parse auth response error | Internal SDK error, please contact us. | Android Only |
| ERROR_NO_PARAM | No available model parameters matched. | Please contact us. | Both |
| LIVENESS_TYPE_NOT_FOUND | Unsupported live type. | Please contact us. | Both |
| LOAD_MODEL_ERROR | Load model error. | Please contact us. | Both |
| APPLICATION_CONTEXT_NULL | ApplicationContext is null | Please ensure that the GuardianLivenessDetectionSDK.init method is called correctly. | Android Only |
| AUTH_NETWORK_ERROR_$ErrorCode | Request network error | Network request failed. If it's an individual user issue, please ask the user to retry on a stable network. If the failure rate is high, please contact us. | Both |
| UPLOAD_IMAGE_DATA_NETWORK_ERROR_$ErrorCode | Upload image data request network error | Network request failed. If it's an individual user issue, please ask the user to retry on a stable network. If the failure rate is high, please contact us. | Both |
| DEVICE_NOT_SUPPORT | Device not supported. | For Android: Typically caused by a damaged camera or a missing .so file. Please ask the user to switch devices. For iOS: There is no available front camera | Both |
| MODEL_ERROR | Model loading error. | For specific error information, please check the message and contact us. | Both |
| USER_GIVE_UP | The user abandoned the detection process. | Based on the user's usage duration, if there is insufficient willingness from the user, please use better guidance to help them complete the liveness detection. If the user repeatedly chooses to abandon the process after a long time, please provide the relevant eventId to us for investigation. For iOS: You need to explicitly enable the recordUserGiveup option in livenessVC to receive this error code when the back button is tapped. | Both |
| UPLOAD_PICTURE_GIVE_UP | The user abandoned the process of uploading liveness images. | If it takes too long and causes the user to abandon it, please ask the user to retry under a stable network. If this error code occurs frequently, please contact us. For iOS: You need to explicitly enable the recordUserGiveup option in livenessVC to receive this error code when the back button is tapped. | Both |
| AUTH_GIVE_UP | The user abandoned the auth request. | If it takes too long and causes the user to abandon it, please ask the user to retry under a stable network. If this error code occurs frequently, please contact us. For iOS: You need to explicitly enable the recordUserGiveup option in livenessVC to receive this error code when the back button is tapped. | Both |
| NO_UPLOAD_IMAGE | The SDK failed to successfully capture the image. | Internal SDK error, please save the eventId and contact us. | Android Only |
| UNDEFINED | Other errors that we have not defined. | Please save the eventId and contact us. | Both |
| ...(Other server side error codes) | Please contact us. | Both |