Getting started
This section introduces the first steps to run our Android SDKs. If you have questions or suggestions, tell us!
Terms & Policies
When using our SDKs, please make sure that you agree with our Privacy Policy and our Terms and Conditions of Use.
Stable versions
DocumentDetector
Compatibility
FaceLiveness
Compatibility
Deprecated versions
Compatibility
Project settings
Add these settings to your app-level build.gradle
:
As our SDKs activities use Data Binding, it is required that you enable this setting within your app. The compileOptions
setting is required for SDK's built-in lambda functions, which were released in Java 8. The noCompress
setting tells the compiler not to compress files with the .tflite
extension used in the DocumentDetector.
Importing the SDKs
Remotely
To import our SDKs, add our maven repository to your project-level build.gradle
:
If you are using the Gradle 7+ version, add our maven repository inside the dependencyResolutionManagement
method in the settings.gradle
file, instead of the build.gradle
:
After that, add the SDK dependency you want to use in your app to the app-level build.gradle
:
ProGuard settings
If you use ProGuard or a similar tool that includes shrink or obfuscation rules in your project, you may need to add these exceptions for our SDKs to work properly.
R8 / PROGUARD
If you are using R8 the shrinking and obfuscation rules are included automatically.
ProGuard users must manually add the options from retrofit2.pro.
Last updated