Android-SDK-Liveness Detection Upgrade (2D)

V2.2.1(2024.4.23)

New Features
Migration Guides
  1. Change the dependency version number to2.2.1

  1. We have found that the class name "LivenessActivity" has been flagged as a risk by platforms such as Kaspersky. Please make sure to rename this class to a different name in order to resolve the warning of "Not-a-virus:HEUR:RiskTool.AndroidOS.SpyLoan.fk".

V2.2.0(2024.2.23)

New Features
Migration Guides
  1. Change the dependency version number to2.2.0

V2.1.9(2024.1.23)

New Features
Migration Guides
  1. Change the dependency version number to2.1.9

  2. Open audit image list functionality.

V2.1.8(2023.12.14)

New Features
Migration Guides
  1. Change the dependency version number to2.1.8

  2. Open audit image list functionality.

  3. Get the audit image list


V2.1.7(2023.12.1)

New Features
Migration Guides
  1. Fllow this link

V2.1.6(2023.11.14)

New Features
Migration Guides
  1. Change the dependency version number to2.1.6


V2.1.5(2023.9.20)

New Features
Migration Guides
  1. Change the dependency version number to2.1.5


V2.1.4(2023.9.7)

New Features
Migration Guides
  1. Change the dependency version number to2.1.4


V2.1.3(2023.4.27)

New Features
Migration Guides
  1. Change the dependency version number to2.1.3


V2.1.2(2023.4.6)

New Features
Migration Guides
  1. Change the dependency version number to2.1.2


V2.1.1(2023.3.23)

New Features
Migration Guides
  1. Change the dependency version number to2.1.1


V1.4.0(2023.2.20)

New Features
Migration Guides
  1. Change the dependency version number to1.4.0


V2.0.2(2022.12.16)

New Features
Migration Guides
  1. Change the dependency version number to2.0.2


V2.0.1(2022.12.06)

New Features
Migration Guides
  1. Change the dependency version number to 2.0.1

  2. Set movement difficulty level(Called before the setLicenseAndCheck() method, otherwise it does not take effect

    You can specify the difficulty of the action detection according to your business requirements (EASY,NORMAL,HARD),default level is NORMAL


V1.3.9 -> V2.0.0(2022.11.25)

New Features
Migration Guides
  1. Change the dependency version number to 2.0.0:

  2. Add new prompt and status code when detecting, add corresponding prompt in status code callback method, otherwise the page will prompt blank. For text resources, please refer to the integration documentation to download the UI source code.


V1.3.8 -> V1.3.9/V1.3.9.x(2022.8.10)

New Features
Migration Guides
  1. Add the following maven repository configuration to your project's build.gradle:

  2. Add library dependencies to the liveness module build.gradle.

  3. Delete liveness_lib_vx.x.x.aarguardian_core_vx.x.aar.

  4. Synchronize gradle to start downloading dependencies

If you are unable to pull the aar, you can download the aar from the following link and manually depend on it for your project.

The links below are for lib 1.3.9.4 and core 3.3. Modify the version number in the link to download the corresponding version.


V1.3.8(2022.7.12)

New Features
Migration Guides

V1.3.7 (2022.6.7)

New features
Migration Guides

V1.3.5 -> V1.3.6 (2022.5.27)

New features
Migration Guides

V1.3.4 -> V1.3.5 (2022.2.18)

New features
Migration Guides

V1.3.3/V1.3.4 (2022.1.13)

New features
Migration Guides

V1.3.2

New features
Migration Guides

V1.3.1

New features
Migration Guides

V1.3.0

New features
Migration Guides

V1.2.9

New features
Migration Guides

V1.2.8

New features
Migration Guides

V1.2.7

New features
Migration Guides

V1.2.6

New features
Migration Guides

V1.2.3

New features
Migration Guides

V1.2.0

New features
Migration Guides

V1.1.9

New features
Migration Guides

V1.1.8

New features

V1.1.7

New features
Migration Guides

V1.1.6

New features
Migration Guides

V1.1.5

New features
Migration Guides

It is recommended to use a full upgrade, the new version of the code is more concise, almost no code intrusion.


V1.1.4

New features
Migration Guides

The original handleResult(ResultEntity entity) method is changed to the callback method onGetFaceDataSuccess() in onDetectionSuccess()
The method content is as follows :

  1. Full Upgrade

    • Copy the liveness\_lib\_v1.1.4.aar and guardian_core_v1.2.aar files to the lives/libs directory and delete the corresponding old version aar. If you also integrate the picture_quality SDK, please replace the SDK dependent guardian_core_vxx.aar with 1.2 Version to avoid version dependency conflicts.
    • add dependency on constraint-layout inliveness/build.gradle:
    • Save the changes you made on LivenessFragment.
    • Overwrite the old file with the new version of the LivenessFragment file, replacing the fragment_liveness.xml layout file.
    • Restore your changes to LivenessFragment.
    • Recompile the project.
  2. Simple upgrade: This update is mainly to optimize the UI module, and solve a small number of bugs in aar. You can choose to replace only the aar file to fix the known problem in aar.

    • Replace the 1.1.3 version file with liveness_lib_v1.1.4.aar and update the reference to 1.1.4 in gradle.

V1.1.3

New features
Migration Guides
1. Get image mode changes from the SDK

Only after the liveness detection test is successful will there be a picture

2.Version Upgrade

V1.1.2

New features
3.Get images from the SDK
3.Migration Guides

There are two ways to upgrade the SDK to version 1.1.2, you can choose one of them according to actual needs.
The new version aar already contains the armeabi schema. If you copied libaailiveness_v1.0.0.so to the libs/armeabi directory during the 1.0 integration process, please delete this .so

Applicable for no custom changes or minor changes to the liveness module code.

  1. Save your custom changes
  2. Remove the liveness module and add dependencies on the new version
  3. Restore your custom changes
Method 2

Suitable for changing the liveness module。No need to delete the old version of the liveness module.

  1. Replace the old aar file in the libs directory with the new liveness_lib_v1.1.2.aar file
  2. Copy guardian_core_v1.0.aar to the libs directory and add a dependency on this aar rebuild project.

tips: If you have not changed the res directory, you can overwrite the old one with the res direct copy in the new liveness library project.