DEVICE_CODE_MINIMUM_OS_VERSION_ERROR

• Code: 8
• Cause: The device's operating system version is lower than the minimum version required to run the SDK.
• Solution: Upgrade the device operating system or use another device.

DEVICE_CODE_CLOCK_SKEW_ERROR

• Code: 17
• Cause: Severe clock skew detected
• Solution: The user should verify that the device date, time and timezone are set correctly. It is recommended to enable 'Set automatically' in the device settings.

DEVICE_CODE_MINIMUM_BROWSER_VERSION_ERROR

• Code: 18
• Cause: The browser version is older than the minimum required version.
• Solution: Upgrade the device's browser or use another browser.

CAMERA_CODE_NO_CAMERA_ERROR

• Code: 1001
• Cause: The session.start() command was called, but the device has no camera with the required specifications.
• Solution: The camera must support a resolution of 640x480 at 30FPS. The user should verify that the device camera works properly.

CAMERA_CODE_CAMERA_OPEN_ERROR

• Code: 1002
• Cause: Could not operate the camera.
• Solution: The user should verify that the device camera works properly and try again. If the problem persists, the user should restart the application.

CAMERA_CODE_CAMERA_MISSING_PERMISSIONS_ERROR

• Code: 1005
• Cause: The application does not have permission to access the camera.
• Solution: The user should grant the web page permission to use the camera.

CAMERA_CODE_UNEXPECTED_IMAGE_DIMENSIONS_WARNING

• Code: 1501
• Cause: The images received from the camera have a different resolution than the requested resolution.
• Solution: Instruct the user to retry taking the measurements. If the problem persists, then the device is probably malfunctioning, or does not support VGA resolution. The user should be instructed to use a different device. Although this is just a "warning" alert, and the measurement continues, the accuracy of the measurement may be impacted by the unexpected resolution.

LICENSE_CODE_ACTIVATION_LIMIT_REACHED_ERROR

• Code: 2002
• Cause: No more devices can be used with your license.
• Solution: Contact the sales team to increase the number of device authorizations in your license.

LICENSE_CODE_METER_ATTRIBUTE_USES_LIMIT_REACHED_ERROR

• Code: 2003
• Cause: No more measurements are allowed for the provided license.
• Solution: Contact the sales team to increase the number of measurements in your license.

LICENSE_CODE_AUTHENTICATION_FAILED_ERROR

• Code: 2004
• Cause: Several issues might cause this error: clock skew detected, the SDK was unable to authenticate the license, a bad token was received from the license server
• Solution: The user should take the following actions: Check the internet connection. Set the device time correctly. Verify that the device has sufficient storage.

LICENSE_CODE_INVALID_LICENSE_KEY_ERROR

• Code: 2007
• Cause: The provided license key is invalid.
• Solution: Use the license key provided by the support team. If the problem persists, contact the support team.

LICENSE_CODE_REVOKED_LICENSE_ERROR

• Code: 2010
• Cause: The license was revoked.
• Solution: Contact the customer support team.

LICENSE_CODE_INTERNAL_ERROR_9

• Code: 2016
• Cause: SSL error. Unable to authenticate the license server response.
• Solution: The user should check the device's local time, internet connection, try a different network, or try again later.

LICENSE_CODE_LICENSE_EXPIRED_ERROR

• Code: 2017
• Cause: The license has expired.
• Solution: Contact the customer support team.

LICENSE_CODE_LICENSE_SUSPENDED_ERROR

• Code: 2018
• Cause: The license is suspended.
• Solution: Contact the customer support team.

LICENSE_CODE_NETWORK_ISSUES_ERROR

• Code: 2024
• Cause: No internet connection.
• Solution: The user should check the internet connection and try again.

LICENSE_CODE_SSL_HANDSHAKE_ERROR

• Code: 2025
• Cause: SSL certificate security warning.
• Solution: The user should check the device's local time, internet connection, try a different network, or try again later.

LICENSE_CODE_INPUT_LICENSE_KEY_EMPTY_ERROR

• Code: 2032
• Cause: No license key was provided to the SDK.
• Solution: Initiate the SDK with a valid license key, provided by the support team.

LICENSE_CODE_INPUT_PRODUCT_ID_ILLEGAL_ERROR

• Code: 2034
• Cause: An invalid product ID was provided.
• Solution: The product ID must be null when establishing a session.

LICENSE_CODE_CANNOT_OPEN_FILE_FOR_READ_ERROR

• Code: 2035
• Cause: The SDK cannot read from the file system, or a file may be corrupted.
• Solution: Instruct the user to check the installation integrity.

LICENSE_CODE_MONTHLY_USAGE_TRACKING_REQUIRES_SYNC_ERROR

• Code: 2036
• Cause: The SDK failed to authenticate with the license server as required by the license type.
• Solution: Instruct the user to check the internet connection and try again.

LICENSE_CODE_SSL_HANDSHAKE_DEVICE_DATE_ERROR

• Code: 2037
• Cause: SSL certificate security warning.
• Solution: The user should check the device's local time, internet connection, try a different network, or try again later.

LICENSE_CODE_SSL_HANDSHAKE_CERTIFICATE_EXPIRED_ERROR

• Code: 2038
• Cause: SSL certificate security warning.
• Solution: The user should check the device's local time, internet connection, try a different network, or try again later.

LICENSE_CODE_MIN_SDK_ERROR

• Code: 2039
• Cause: The SDK version is too old to be used with this license.
• Solution: Upgrade to the latest SDK version or contact the support team.

LICENSE_CODE_NETWORK_TIMEOUT_ERROR

• Code: 2042
• Cause: Network timeout reached for a single call
• Solution: Advise the user to try the following steps: verify the internet connection speed, restart the application, wait briefly, attempt using another network, or try again later. If the issue persists, please contact our support team.

MEASUREMENT_CODE_MISDETECTION_DURATION_EXCEEDS_LIMIT_ERROR

• Code: 3003
• Cause: The face was not detected for a period of over 0.5 seconds several times.
• Solution: The user should ensure that the face remains still during the measurement and follow the best practices provided by the provider for taking accurate measurements.

MEASUREMENT_CODE_INVALID_RECENT_DETECTION_RATE_ERROR

• Code: 3004
• Cause: More than two periods of multiple frame losses were detected during the measurement. This issue may occur if the device is overloaded and unable to process video frames in real-time, or if there is insufficient lighting on the user's face.
• Solution: For the User: - Ensure the device is not overloaded, overheated, or running low on resources. - Improve the lighting on your face to enhance SDK performance. - If the problem persists, close other applications or services, or restart the device. - Follow best practices for taking a measurement and provide guidance on optimizing device performance. For the Application Developer: - Avoid using debugging or developer tools or performing intensive logging during the measurement.

MEASUREMENT_CODE_LICENSE_ACTIVATION_FAILED_ERROR

• Code: 3006
• Cause: The license activation failed.
• Solution: The user should check the device's internet connection, and should check that no invalid proxy configuration is used. If the problem persists, the user should contact the support team.

MEASUREMENT_CODE_INVALID_MEASUREMENT_AVERAGE_DETECTION_RATE_ERROR

• Code: 3008
• Cause: The average frame rate is significantly lower than expected. This issue may result from device overloading or insufficient lighting on the user's face.
• Solution: For the User: Close resource-intensive applications to free up device resources. Ensure the device is not busy, overheated, or overloaded. Allow the device to cool down and retry the measurement. If the problem persists, consider using another device. For the Application Developer: Verify that the SDK implementation does not impose excessive demands on the device. Provide users with clear instructions to optimize their device performance and follow best practices for taking a measurement. Ensure your application minimizes background activity during SDK operations.

MEASUREMENT_CODE_TOO_MANY_FRAMES_INORDER_ERROR

• Code: 3009
• Cause: Multiple consecutive frames were received in incorrect timestamp order. This error occurs if warning 3506 is issued multiple times.
• Solution: The user should rerun the measurement.

MEASUREMENT_CODE_MISDETECTION_DURATION_EXCEEDS_LIMIT_WARNING

• Code: 3500
• Cause: A face was not detected for a period of over 0.5 seconds.
• Solution: The instantaneous vital signs should not be displayed to the user for a few seconds until the algorithms overcome the detection issues. The user must follow the best practices for taking a measurement.

MEASUREMENT_CODE_INVALID_RECENT_FPS_RATE_WARNING

• Code: 3505
• Cause: Camera FPS is degraded and may affect the measurement quality.
• Solution: The user should make sure to follow the best practices for taking a measurement.

MEASUREMENT_CODE_MEASUREMENT_MISPLACED_FRAME_WARNING

• Code: 3506
• Cause: A frame was received in incorrect timestamp order.
• Solution: The user should proceed with the measurement.

VITAL_SIGN_CODE_BLOOD_PRESSURE_PROCESSING_FAILED_WARNING

• Code: 4505
• Cause: Failure to calculate blood pressure in this measurement. This warning does not impact other vital sign measurements. The failure may have been caused by corrupted installation files.
• Solution: Blood pressure will not be calculated for this measurement session. The other vital sign results will be presented. The user can retry the measurement. If the problem persists, the user should reinstall/repair the app.

VITAL_SIGN_CODE_MEASURING_WITH_NO_ENABLED_VITAL_SIGNS_WARNING

• Code: 4506
• Cause: No vital signs were processed as part of this measurement.
• Solution: This warning is issued when the license does not support the calculation of any vital signs, or when the SDK cannot access license information. The user should check the internet connection and try another measurement.

SESSION_CODE_ILLEGAL_START_CALL_ERROR

• Code: 6004
• Cause: A session start call was made when the session is not in READY state
• Solution: Wait for session state to become READY before calling start.

SESSION_CODE_ILLEGAL_STOP_CALL_ERROR

• Code: 6005
• Cause: A session stop call was made when the session is not in PROCESSING state
• Solution: Call stop only when session is processing.

INITIALIZATION_CODE_INVALID_PROCESSING_TIME_ERROR

• Code: 7002
• Cause: An invalid session time was provided when creating a session.
• Solution: Use a valid session time. The valid session time range is between 20-180 seconds.

INITIALIZATION_CODE_INVALID_LICENSE_FORMAT

• Code: 7005
• Cause: The provided license key is either empty or its format is invalid.
• Solution: Check the SDK license key provided by the support team. Ensure it is not empty and follows a valid format - avoid including spaces, newlines, or special characters.

INITIALIZATION_CODE_SDK_LOAD_FAILURE

• Code: 7006
• Cause: The SDK fails to load the algorithmic binary file (a.wasm.gz).
• Solution: Make sure a.wasm.gz is white listed and is deliverable by the server.

INITIALIZATION_CODE_UNSUPPORTED_USER_WEIGHT

• Code: 7007
• Cause: The weight submitted by the user is not supported. The supported weight range is between 40 to 200 kilograms.
• Solution: The user should either submit a weight within the supported range, or not specify a weight at all.

INITIALIZATION_CODE_UNSUPPORTED_USER_AGE

• Code: 7008
• Cause: The age submitted by the user is not supported. The supported age range is between 18 to 110 years.
• Solution: The user should either submit an age within the supported range or not specify an age at all.

INITIALIZATION_CODE_CONCURRENT_SESSIONS_ERROR

• Code: 7009
• Cause: Trying to create a new session before terminating the previous session.
• Solution: The previous session should be terminated before establishing a new one.

INITIALIZATION_CODE_UNSUPPORTED_USER_HEIGHT

• Code: 7012
• Cause: The height submitted by the user is not supported. The supported height range is between 130 to 230 centimeters.
• Solution: The application should specify a height value within the supported range or not specify a height at all.

INITIALIZATION_CODE_MEMORY_ALLOCATION_ERROR

• Code: 7013
• Cause: The memory allocation failed due to an internal bug in Emscripten when running on iOS 17 or earlier. This is caused due to several invocations of the SDK in the same tab one after the other, e.g. when ‘refreshing’ the page several times. For additional information see https://bugs.webkit.org/show_bug.cgi?id=222097#c17.
• Solution: To mitigate this, it is recommended that each measurement be initiated in a new tab. If this issue arises, advise the user to restart the browser or open the page in a new tab (provide a clickable link while preserving the context) and continue as normal. This Webkit issue has been resolved in iOS 18. For further information, refer to https://bugs.webkit.org/show_bug.cgi?id=222097#c17 and https://bugs.webkit.org/show_bug.cgi?id=255103.

INITIALIZATION_CODE_INITIAL_MEMORY_ALLOCATION_ERROR

• Code: 7014
• Cause: Memory allocation failure
• Solution: Instruct the user to close all other applications and active browser tabs, wait for a few seconds and try again. If the problem still persists it means the device is too weak to run the SDK.

INITIALIZATION_CODE_BROWSER_NOT_SUPPORTING_SHARED_ARRAY_BUFFER_ERROR

• Code: 7015
• Cause: The user's browser does not support SharedArrayBuffer.
• Solution: Instruct the user to upgrade the browser's version or use another browser/device.

INITIALIZATION_MEMORY_CONSUMPTION_WARNING

• Code: 7501
• Cause: The application is attempting to invoke the SDK in a tab where it has been invoked before. Due to an internal bug in Emscripten for iOS17 and below there is a potential memory leak that might prevent running the SDK properly.
• Solution: Recurring SDK invocations within the same tab (e.g., refreshing the page multiple times) can result in a memory leak, which may eventually lead to memory allocation failures. To mitigate this, it is recommended that each measurement be initiated in a new tab. If this issue arises, advise the user to restart the browser or open the page in a new tab (provide a clickable link while preserving the context) and continue as normal. This Webkit issue has been resolved in iOS 18. For further information, refer to Webkit https://bugs.webkit.org/show_bug.cgi?id=222097#c17 and Webkit https://bugs.webkit.org/show_bug.cgi?id=255103.