CocoaPods

To integrate OZLivenessSDK into an Xcode project via the CocoaPods dependency manager, add the following code to Podfile:

pod 'OZLivenessSDK', :git => 'https://gitlab.com/oz-forensics/oz-liveness-ios', :tag => 'VERSION'

Version is optional as, by default, the newest version is integrated. However, if necessary, you can find the older version number in Changelog.

Since 8.1.0, you can also use a simpler code:

// for the latest version
pod ‘OZLivenessSDK’
// OR, for the specific version
// pod ‘OZLivenessSDK’, ‘8.10.0’

By default, the full version is being installed. It contains both server-based and on-device analysis modes. To install the server-based version only, use the following code:

pod 'OZLivenessSDK/Core', :git => 'https://gitlab.com/oz-forensics/oz-liveness-ios.git',  :tag => 'VERSION'

For 8.1.0 and higher:

pod ‘OZLivenessSDK/Core’
// OR
// pod ‘OZLivenessSDK/Core’, ‘8.1.0’

SPM

Please note: installation via SPM is available for versions 8.7.0 and above.

Add the following package dependencies via SPM: https://gitlab.com/oz-forensics/oz-mobile-ios-sdk (if you need a guide on adding the package dependencies, please refer to the Apple documentation). OzLivenessSDK is mandatory. If you don't need the on-device analyses, skip the OzLivenessSDKOnDevice file.

Manual Installation

You can also add the necessary frameworks to your project manually.

1. Download the SDK files from here and add them to your project.

• OZLivenessSDK.xcframework,

• OZLivenessSDKResources.bundle,

• OZLivenessSDKOnDeviceResources.bundle (if you don't need the on-device analyses, skip this file).

1. Download the TensorFlow framework 2.11 from here.

2. Make sure that:

• both xcframework are in Target-Build Phases -> Link Binary With Libraries and Target-General -> Frameworks, Libraries, and Embedded Context;

• the bundle file(s) are in Target-Build Phases -> Copy Bundle Resources.

You can generate the trial license here or contact us by email to get a productive license. To create the license, your applicationId (bundle id) is required.

To pass your license file to the SDK, call the OzLivenessSDK.init method with a list of LicenseSources. Use one of the following:

• LicenseSource.LicenseAssetId should contain a path to a license file called forensics.license, which has to be located in the project's res/raw folder.

• LicenseSource.LicenseFilePath should contain a file path to the place in the device's storage where the license file is located.

OzLivenessSDK.init(context,
    listOf(
        LicenseSource.LicenseAssetId(R.raw.your_license_name),
        LicenseSource.LicenseFilePath("absolute_path_to_your_license_file")
    ),
    object : StatusListener<LicensePayload> {
        override fun onSuccess(result: LicensePayload) { /*check the license payload*/ }
        override fun onError(error: OzException) { /*handle the exception */ }
    }
  )

OzLivenessSDK.INSTANCE.getConfig().setBaseURL(BASE_URL);
OzLivenessSDK.INSTANCE.init(context,
    Arrays.asList(
        new LicenseSource.LicenseAssetId(R.raw.forensics),
        new LicenseSource.LicenseFilePath("absolute_path_to_your_license_file")
    ),
    new StatusListener<LicensePayload>() {
        @Override public void onStatusChanged(@Nullable String s) {}
        @Override public void onSuccess(LicensePayload licensePayload) { /*check the license payload*/ }
        @Override public void onError(@NonNull OzException e) { /*handle the exception */ }
    }
);

In case of any license errors, the onError function is called. Use it to handle the exception as shown above. Otherwise, the system will return information about license. To check the license data manually, use the getLicensePayload method.

Possible License Errors

Add the following URL to the build.gradle of the project:

allprojects {
  repositories {
    maven { url "https://ozforensics.jfrog.io/artifactory/main" }
  }
}

Add this to the build.gradle of the module (VERSION is the version you need to implement. Please refer to Changelog):

for the server-based version only

Please note: this is the default version.

dependencies {
  implementation 'com.ozforensics.liveness:sdk:VERSION'
}

for both server-based and on-device versions

Please note: the resulting file will be larger.

dependencies {
implementation 'com.ozforensics.liveness:full:VERSION'
}

Also, regardless of the mode chosen, add:

android {
  compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
  }
}

The common way of Oz Mobile SDK to work is the server-based mode, when the Liveness and Biometry analyses are performed on a server as shown in the scheme below:

But there's also an option to perform checks without server calls or even Internet connection. This option stands for on-device analyses.

The on-device analyses are being performed faster and more secure as all data is processed directly on device, nothing is being sent anywhere. In this case, you don’t need a server at all, neither need you the API connection.

The on-device analysis mode is useful when:

• you do not collect, store or process personal data;

• you need to identify a person quickly regardless of network conditions such as a distant region, inside a building, underground, etc.;

• you’re on a tight budget as you can save money on the hardware part.

Launching the On-Device Analysis

To launch the on-device check, set the appropriate mode for Android or iOS SDK.

Android:

analysisCancelable = AnalysisRequest.Builder()
    .addAnalysis(Analysis(Analysis.Type.QUALITY, Analysis.Mode.ON_DEVICE, mediaToAnalyze))

analysisCancelable = new AnalysisRequest.Builder()
    .addAnalysis(new Analysis(Analysis.Type.QUALITY, Analysis.Mode.ON_DEVICE, mediaList)) 

iOS:

let analysis = Analysis.init(media: mediaToAnalyze, type: .quality, mode: .onDevice)

For details, please refer to the Checking Liveness and Face Biometry sections for iOS and Android.

Oz Mobile SDK stands for the Software Developer’s Kit of the Oz Forensics Liveness and Face Biometric System, providing seamless integration with customers’ mobile apps for login and biometric identification.

Master license is the offline license that allows using Mobile SDKs with any bundle_id, unlike the regular licenses. To get a master license, create a pair of keys as shown below. Email us the public key, and we will email you the master license shortly after that. Your application needs to sign its bundle_id with the private key, and the Mobile SDK checks the signature using the public key from the master license. Master licenses are time-limited.

Generating Keys

This section describes the process of creating your private and public keys.

Creating a Private Key

To create a private key, run the commands below one by one.

openssl genpkey -algorithm RSA -outform DER -out privateKey.der -pkeyopt rsa_keygen_bits:2048
# for MacOS
base64 -i privateKey.der -o privateKey.txt
# for Linux 
base64 -w 0 privateKey.der > privateKey.txt

You will get these files:

• privateKey.der is a private .der key;

• privateKey.txt is privateKey.der encoded by base64. This key containing will be used as the host app bundle_id signature.

File examples:

The OpenSSL command specification: https://www.openssl.org/docs/man1.1.1/man1/openssl-pkcs8.html

Creating a Public Key

To create a public key, run this command.

openssl rsa -pubout -in privateKey.der -out publicKey.pub

You will get the public key file: publicKey.pub. To get a license, please email us this file. We will email you the license.

File example:

SDK Integration

SDK initialization:

fun init(
    context: Context,
    licenseSources: List<LicenseSource>,
    masterLicenseSignature: String,
    statusListener: StatusListener<LicensePayload>? = null,
)

Prior to the SDK initializing, create a base64-encoded signature for the host app bundle_id using the private key.

Signature creation example:

private fun getMasterSignature(): String {
    Security.insertProviderAt(org.spongycastle.jce.provider.BouncyCastleProvider(), 1)

    val privateKeyBase64String = "the string copied from the privateKey.txt file"
    // with key example:
    // val privateKeyBase64String = "MIIEpAIBAAKCAQEAxnpv02nNR34uNS0yLRK1o7Za2hs4Rr0s1V1/e1JZpCaK8o5/3uGV+qiaTbKqU6x1tTrlXwE2BRzZJLLQdTfBL/rzqVLQC/n+kAmvsqtHMTUqKquSybSTY/zAxqHF3Fk59Cqisr/KQamPh2tmg3Gu61rr9gU1rOglnuqt7FioNMCMvjW7ciPv+jiawLxaPrzNiApLqHVN+xCFh6LLb4YlGRaNUXlOgnoLGWSQEsLwBZFkDJDSLTJheNVn9oa3PXg4OIlJIPlYVKzIDDcSTNKdzM6opkS5d+86yjI1aTKEH3Zs64+QoEuoDfXUxS3TOUFx8P+wfjOR5tYAT+7TRN4ocwIDAQABAoIBAATWJPV05ZCxbXTURh29D/oOToZ0FVn78CS+44Vgy1hprAcfG9SVkK8L/r6X9PiXAkNJTR+Uivly64Oua8//bNC7f8aHgxRXojFmWwayj8iOMBncFnad1N2h4hy1AnpNHlFp3I8Yh1g0RpAZOOVJFucbTxaup9Ev0wLdWyGgQ3ENmRXAyLU5iUDwUSXg59RCBFKcmsMT2GmmJt1BU4P3lL9KVyLBktqeDWR/l5K5y8pPo6K7m9NaOkynpZo+mHVoOTCtmTj5TC/MH9YRHlF15VxQgBbZXuBPxlYoQCsMDEcZlMBWNw3cNR6VBmGiwHIc/tzSHZVsbY0VRCYEbxhCBZkCgYEA+Uz0VYKnIWViQF2Na6LFuqlfljZlkOvdpU4puYTCdlfpKNT3txYzO0T00HHY9YG9k1AW78YxQwsopOXDCmCqMoRqlbn1SBe6v49pVB85fPYU2+L+lftpPlx6Wa0xcgzwOBZonHb4kvp1tWhUH+B5t27gnvRz/rx5jV2EfmWinycCgYEAy8/aklZcgoXWf93N/0EZcfzQo90LfftkKonpzEyxSzqCw7B9fHY68q/j9HoP4xgJXUKbx1Fa8Wccc0DSoXsSiQFrLhnT8pE2s1ZWvPaUqyT5iOZOW6R+giFSLPWEdwm6+BeFoPQQFHf8XH3Z2QoAepPrEPiDoGN1GSIXcCwoe9UCgYEAgoKj4uQsJJKT1ghj0bZ79xVWQigmEbE47qI1u7Zhq1yoZkTfjcykc2HNHBaNszEBks45w7qo7WU5GOJjsdobH6kst0eLvfsWO9STGoPiL6YQE3EJQHFGjmwRbUL7AK7/Tw2EJG0wApn150s/xxRYBAyasPxegTwgEj6j7xu7/78CgYEAxbkI52zG5I0o0fWBcf9ayx2j30SDcJ3gx+/xlBRW74986pGeu48LkwMWV8fO/9YCx6nl7JC9dHI+xIT/kk8OZUGuFBRUbP95nLPHBB0Hj50YRDqBjCBh5qaizSEGeGFFNIfFSKddri3U8nnZTNiKLGCx7E3bjE7QfCh5qoX8ZF0CgYAtsEPTNKWZKA23qTFI+XAg/cVZpbSjvbHDSE8QB6X8iaKJFXbmIC0LV5tQO/KT4sK8g40m2N9JWUnaryTiXClaUGU3KnSlBdkIA+I77VvMKMGSg+uf4OdfJvvcs4hZTqZRdTm3dez8rsUdiW1cX/iI/dJxF4964YIFR65wL+SoRg=="
    val sig = Signature.getInstance("SHA512WithRSA")
    val keySpec = PKCS8EncodedKeySpec(Base64.decode(privateKeyBase64String, Base64.DEFAULT))
    val keyFactory = KeyFactory.getInstance("RSA")
    sig.initSign(keyFactory.generatePrivate(keySpec))
    sig.update(packageName.toByteArray(Charsets.UTF_8))
    return Base64.encodeToString(sig.sign(), Base64.DEFAULT).replace("\n", "")
}

KohJ1rsUgLMzZHpHGAZDK2efHPnMj9tw9VIedBLvyZt0B2JH3SWfJLJ8X6JNz3bR2sce6PR2wdEIFln0r1pUnD+6WBCgexKIHAv7esiRVQZoZOEANDBwDvJVv73H/0qL2LGlhxKzbBg5CxGPClTBQdLo1P+7HsTXHHG/Hf6m3rdu1OUeGXVPoaS2NzE8kiRH6gb8Nhr7PBLTUeMKTeLoiX13hvwjOqhV1ANhgS97T4hC2+ZilZt4RektgRY/+fGmWnOqErNeYuz/WSInfaJS0YEWhJW3gXKPjdCzNGIBIqbxaFSjU46wu/alh2+tBRFnrYFl1dRQVcTlW0VwwZHcug==

Pass the signature as the masterLicenseSignature parameter during the SDK initialization.

If the signature is invalid, the initialization continues as usual: the SDK checks the list of bundle_id included into the license, like it does it by default without a master license.

If you use our SDK just for capturing videos, omit this step.

To check liveness and face biometry, you need to upload media to our system and then analyze them.

Here’s an example of performing a check:

analysisCancelable = AnalysisRequest.Builder()
 // mediaToAnalyze is an array of OzAbstractMedia that were captured or otherwise created 
    .addAnalysis(Analysis(Analysis.Type.QUALITY, Analysis.Mode.SERVER_BASED, mediaToAnalyze))// or ON_DEVICE if you want the on-device analysis
    .build()
//initiating the analyses and setting up a listener
    .run(object : AnalysisRequest.AnalysisListener {
        override fun onStatusChange(status: AnalysisRequest.AnalysisStatus) { handleStatus(status) // or your status handler
        }
        override fun onSuccess(result: RequestResult) {
            handleResults(result) // or your result handler
        }
        override fun onError(error: OzException) { handleError(error) // or your error handler 
        }
    })

analysisCancelable = new AnalysisRequest.Builder()
// mediaToAnalyze is an array of OzAbstractMedia that were captured or otherwise created 
        .addAnalysis(new Analysis(Analysis.Type.QUALITY, Analysis.Mode.SERVER_BASED, mediaToAnalyze)) // or ON_DEVICE if you want the on-device analysis
        .build()
//initiating the analyses and setting up a listener
        .run(new AnalysisRequest.AnalysisListener() { 
            @Override
            public void onSuccess(@NonNull RequestResult list) { handleResults(list); } // or your result handler
            @Override
            public void onError(@NonNull OzException e) { handleError(e); } // or your error handler
            @Override
            public void onStatusChange(@NonNull AnalysisRequest.AnalysisStatus analysisStatus) { handleStatus(analysisStatus); } // or your status handler
        })

To delete media files after the checks are finished, use the clearActionVideos method.

Adding Metadata

To add metadata to a folder, use the addFolderMeta method.

    .addFolderMeta(
        mapOf(
            "key1" to "value1",
            "key2" to "value2"
        )
    )

.addFolderMeta(Collections.singletonMap("key", "value")) 

Extracting the Best Shot

In the params field of the Analysis structure, you can pass any additional parameters (key + value), for instance, to extract the best shot on the server side.

mapOf("extract_best_shot" to true)

Using Media from Another SDK

To use a media file that is captured with another SDK (not Oz Android SDK), specify the path to it in OzAbstractMedia:

       val file = File(context.filesDir, "media.mp4") // use context.getExternalFilesDir(null) instead of context.filesDir for external app storage
       val media = OzAbsractMedia.OzVideo(OzMediaTag.VideoSelfieSmile, file.absolutePath)

Adding Media to a Certain Folder

If you want to add your media to the existing folder, use the setFolderId method:

    .setFolderId(folderId)

To connect SDK to Oz API, specify the API URL and access token as shown below.

OzLivenessSDK.setApiConnection(OzConnection.fromServiceToken(host, token))

OzLivenessSDK.INSTANCE.setApiConnection(
        OzConnection.Companion.fromServiceToken(host, token), 
        null
);

Alternatively, you can use the login and password provided by your Oz Forensics account manager:

OzLivenessSDK.setApiConnection(
    OzConnection.fromCredentials(host, username, password),
    statusListener(
        { token -> /* token */ },
        { ex -> /* error */ }
    )
)

OzLivenessSDK.INSTANCE.setApiConnection(
        OzConnection.Companion.fromCredentials(host, username, password),
        new StatusListener<String>() {
            @Override
            public void onStatusChanged(@Nullable String s) {}
            @Override
            public void onSuccess(String token) { /* token */ }
            @Override
            public void onError(@NonNull OzException e) { /* error */ }
        }
);

Although, the preferred option is authentication via access token – for security reasons.

By default, logs are saved along with the analyses' data. If you need to keep the logs distinct from the analysis data, set up the separate connection for telemetry as shown below:

OzLivenessSDK.setEventsConnection(
    OzConnection.fromCredentials(
        "https://tm.ozforensics.com/",
        "<your_telemetry_user_eg_tm@company.com>",
        "your_telemetry_password"
    )
)

OzLivenessSDK.setEventsConnection(
        OzConnection.fromCredentials(
                "https://tm.ozforensics.com/",
                "<your_telemetry_user_eg_tm@company.com>",
                "your_telemetry_password"
        )
);

Clearing authorization:

OzLivenessSDK.setApiConnection(null)

OzLivenessSDK.INSTANCE.setApiConnection(null, null);

Other Methods

Check for the presence of the saved Oz API access token:

val isLoggedIn = OzLivenessSDK.isLoggedIn

boolean isLoggedIn = OzLivenessSDK.INSTANCE.isLoggedIn();

LogOut:

OzLivenessSDK.logout()

OzLivenessSDK.INSTANCE.logout();

To start recording, use thestartActivityForResult method:

To obtain the captured video, use theonActivityResult method:

If a user closes the capturing screen manually, resultCode receives the Activity.RESULT_CANCELED value.

Code example:

Configuration

We recommend applying these settings when starting the app.

Interface Customization

By default, SDK uses the locale of the device. To switch the locale, use the code below:

Please note: this feature has been implemented in 8.1.0.

To add or update the language pack for Oz Android SDK, please follow these instructions:

1. Go to the folder for the locale needed, or create a new folder. Proceed to this guide for the details.

2. Create the file called strings.xml.

3. Copy the strings from the attached file to your freshly created file.

4. Redefine the strings you need in the appropriate localization records.

A list of keys for Android:

The keys action_*_go refer to the appropriate gestures. Others refer to the hints for any gesture, info messages, or errors.

When new keys appear with new versions, if no translation is provided in your file, the new strings are shown in English.

To start using Oz Android SDK, follow the steps below.

1. Embed Oz Android SDK into your project as described here.

2. Get a trial license for SDK on our website or a production license by email. We'll need your application id. Add the license to your project as described here.

3. Connect SDK to API as described here. This step is optional, as this connection is required only when you need to process data on a server. If you use the on-device mode, the data is not transferred anywhere, and no connection is needed.

4. Capture videos using methods described here. You'll send them for analysis afterward.

5. Analyze media you've taken at the previous step. The process of checking liveness and face biometry is described here.

6. If you want to customize the look-and-feel of Oz Android SDK, please refer to this section.

Resources

Recommended Android version: 5+ (the newer the smartphone is, the faster the analyses are).

Recommended versions of components:

We do not support emulators.

Available languages: EN, ES, HY, KK, KY, TR, PT-BR.

To obtain the sample apps source code for the Oz Liveness SDK, proceed to the GitLab repository:

Follow the link below to see a list of SDK methods and properties:

Download the demo app latest build here.

To start using Oz iOS SDK, follow the steps below.

Resources

Minimal iOS version: 11.

Minimal Xcode version: 15 for versions 8.10.0 and newer.

Available languages: EN, ES, HY, KK, KY, TR, PT-BR.

A sample app source code using the Oz Liveness SDK is located in the GitLab repository:

Follow the link below to see a list of SDK methods and properties:

8.16.2 – Mar. 19, 2025

• Resolved the issue with possible SDK crashes when closing the Liveness screen.

8.16.1 – Mar. 14, 2025

• Security updates.

8.16 – Mar. 11, 2025

• Updated the authorization logic.

• Improved voiceover.

• Fixed the issue with SDK lags and the non-responding error that users might have encountered on some devices after completing the video recording.

• Resolved the issue with SDK crashes on some devices that might have occurred because of trying to access non-initialized or closed resources.

• Security updates.

8.15.6 – Feb. 26, 2025

• Security updates.

8.15.5 – Feb. 18, 2025

• You can now disable video validation that has been implemented to avoid recording of extremely short videos (3 frames and less): switch the option off using disableFramesCountValidation.

• Fixed the bug with green videos on some smartphone models.

• Security updates.

8.15.4 – Feb. 11, 2025

• Fixed bugs that could have caused crashes on some phone models.

8.15.0 – Dec. 30, 2024

• Changed the wording for the head_down gesture: the new wording is “tilt down”.

• Added proper focus order for TalkBack when the antiscam hint is enabled.

• Added the public setting extract_action_shot in the Demo Application.

• Fixed bugs.

• Security updates.

8.14.1 – Dec. 5, 2024

• Fixed the bug when the recorded videos might appear green.

• Resolved codec issues on some smartphone models.

8.14.0 – Dec. 2, 2024

• Accessibility updates according to WCAG requirements: the SDK hints and UI controls can be voiced.

• Improved user experience with head movement gestures.

• Moved the large video compression step to the Liveness screen closure.

• Fixed the bug when the best shot frame could contain an image with closed eyes.

• Minor bug fixes and telemetry updates.

8.13.0 – Nov. 12, 2024

• Security and telemetry updates.

8.12.4 – Oct. 01, 2024

• Security updates.

8.12.2 – Sept. 10, 2024

• Security updates.

8.12.0 – Aug. 29, 2024

• Security and telemetry updates.

8.11.0 – Aug. 19, 2024

• Fixed the RuntimeException error with the server-based Liveness that appeared on some devices.

• Security updates.

8.10.0 – July 26, 2024

• Security updates.

• Bug fixes.

8.9.0 – July 18, 2024

• Updated the Android Gradle plugin version to 8.0.0.

• Internal SDK improvements.

8.8.3 – July 11, 2024

• Internal SDK improvements.

8.8.2 – June 21, 2024

• Security updates.

8.8.1 – June 12, 2024

• Security updates.

8.8.0 – June 04, 2024

• Security updates.

8.7.3 – June 03, 2024

• Security updates.

8.7.0 – May 06, 2024

• Added a description for the error that occurs when providing an empty string as an ID in the setFolderID method.

• Fixed a bug causing an endless spinner to appear if the user switches to another application during the Liveness check.

• Fixed some smartphone model specific-bugs.

8.6.0 – Apr. 05, 2024

• Upgraded the on-device Liveness model.

• Security updates.

8.5.0 – Feb. 27, 2024

• The length of the Selfie gesture is now configurable (affects the video file size).

• You can set your own logo instead of Oz logo if your license allows it.

• Removed the pause after the Scan gesture.

• If the recorded video is larger than 10 MB, it gets compressed.

• Security and logging updates.

8.4.4 – Feb. 06, 2024

• Changed the master license validation algorithm.

8.4.3 – Jan. 29, 2024

• Downgraded the required compileSdkVersion from 34 to 33.

8.4.2 – Jan. 15, 2024

• Security updates.

8.4.0 – Jan. 04, 2024

• Updated the on-device Liveness model.

• Fixed some bugs.

8.3.3 – Dec. 11, 2023

• Internal licensing improvements.

8.3.2 – Nov. 30, 2023

• Internal SDK improvements.

8.3.1 – Nov. 24, 2023

• Bug fixes.

8.3.0 – Nov. 17, 2023

• Implemented the possibility of using a master license that works with any bundle_id.

• Video compression failure on some phone models is now fixed.

8.2.1 – Nov. 01, 2023

• Bug fixes.

8.2.0 – Oct. 23, 2023

• The Analysis structure now contains the sizeReductionStrategy field. This field defines what type of media is being sent to the server in case of the hybrid analysis once the on-device analysis is finished successfully.

• The messages for the errors that are retrieved from API are now detailed.

8.1.1 – Oct. 02, 2023

• If multiple analyses are applied to the folder simultaneously, the system sends them as a group. It means that the “worst” of the results will be taken as resolution, not the latest. Please refer to this article for details.

• For the Liveness analysis, the system now treats the highest score as a quantitative result. The Liveness analysis output is described here.

8.1.0 – Sept. 07, 2023

• Updated the Liveness on-device model.

• Added the Portuguese (Brazilian) locale.

• You can now add a custom or update an existing language pack. The instructions can be found here.

• If a media hasn't been uploaded correctly, the system repeats the upload.

• Created a new method to retrieve the telemetry (logging) identifier: getEventSessionId.

• The login and auth methods are now deprecated. Use the setAPIConnection method instead.

• OzConfig.baseURL and OzConfig.permanentAccessToken are now deprecated.

• If a user closes the screen during video capture, the appropriate error is now being handled by SDK.

• Fixed some bugs and improved the SDK work.

8.0.3 – Aug. 24, 2023

• Fixed errors.

8.0.2 – July 13, 2023

• The SDK now works properly with baseURL set to null.

8.0.1 – June 28, 2023

• The dependencies' versions have been brought into line with Kotlin version.

8.0.0 – June 19, 2023

• Added the new analysis mode – hybrid (Liveness only). If the score received from an on-device analysis is too high, the system initiates a server-based analysis as an additional check.

• Kotlin version requirements lowered to 1.7.21.

• Improved the on-device models.

• For some phone models, fixed the fatal device error.

• The hint text width can now exceed the frame width (when using the main camera).

• Photos taken during the One Shot analysis are now being sent to the server in the original size.

• Removed the OzAnalysisResult class. The onSuccess method ofAnalysisRequest.run now uses the RequestResult structure instead of List<OzAnalysisResult>.

• All exceptions are moved to the com.ozforensics.liveness.sdk.core.exceptions package (See changes below).

• Classes related to AnalysisRequest are moved to the com.ozforensics.liveness.sdk.analysispackage (See changes below).

• The methods below are no longer supported:

7.3.1 – June 07, 2023

• Restructured the settings screen.

• Added the center hint background customization.

• Added new face frame forms (Circle, Square).

• Added the antiscam widget and its customization. This feature allows you to alert your customers that the video recording is being conducted, for instance, for loan application purposes. The purpose of this is to safeguard against scammers who may attempt to deceive an individual into approving a fraudulent transaction.

• The OzLivenessSDK::init method no longer crashes if there is a StatusListener parameter passed.

• Changed the scan gesture animation.

7.2.0 – May 04, 2023

• Improved the SDK algorithms.

7.1.4 – Mar. 30, 2023

• Updated the model for the on-device analyses.

• Fixed the animation for sunglasses/mask.

• The oval size for Liveness is now smaller.

7.1.3 – Mar. 03, 2023

• Fixed the error with the server-based analyses while using permanentAccessToken for authorization.

7.1.2 – Feb. 22, 2023

• Added customization for the hint animation.

• You can now hide the status bar and system buttons (works with 7.0.0 and higher).

• OzLivenessSDK.init now requires context as the first parameter.

• OzAnalysisResult now shows the server-based analyses' scores properly.

• Fixed initialization issues, displaying of wrong customization settings, authorization failures on Android <7.1.1.

7.1.1 – Jan. 16, 2023

• Fixed crashes for Android v.6 and below.

• Fixed oval positioning for some phone models.

• Internal fixes and improvements.

7.1.0 – Dec. 16, 2022

• Updated security.

• Implemented some internal improvements.

• The addMedia method is now deprecated, please use uploadMedia for uploading.

7.0.0 – Nov. 23, 2022

• Changed the way of sharing dependencies. Due to security issues, now we share two types of libraries as shown below: sdk is a server analysis only, full provides both server and on-device analyses:

implementation 'com.ozforensics.liveness:full:7.0.0'
implementation 'com.ozforensics.liveness:sdk:7.0.0'

• UICustomization has been implemented instead of OzCustomization.

• Implemented a range of UI customization options and switched to the new design. To restore the previous settings, please refer to this article.

• Added the Spanish locale.

6.4.2.3

• Fixed the bug with freezes that had appeared on some phone models.

• SDK now captures videos in 720p.

6.4.1

• Synchronized the names of the analysis modes with iOS: SERVER_BASED and ON_DEVICE.

• Fixed the bug with displaying of localization settings.

6.4.0

• Now you can use Fragment as Liveness screen.

• Added a new field to the Analysis structure. The params field is for any additional parameters, for instance, if you need to set extracting the best shot on server to true. The best shot algorithm chooses the most high-quality frame from a video.

6.3.7

• The Zoom in and Zoom out gestures are no longer supported.

6.3.6

• Updated the biometry model.

6.3.5

• Added a new simplified API – AnalysisRequest. With it, it’s easier to create a request for the media and analysis you need.

6.3.4

• Published the on-device module for on-device liveness and biometry analyses. To add this module to your project, use:

    implementation 'com.ozforensics.liveness:on-device:6.3.4'

To launch these analyses, use runOnDeviceBiometryAnalysis and runOnDeviceLivenessAnalysis methods from the OzLivenessSDK class:

val mediaList: List<OzAbstractMedia> = ...
val biometryAnalysisResult: OzAnalysisResult = OzLivenessSDK.runOnDeviceBiometryAnalysis(mediaList)
val livenessAnalysisResult: OzAnalysisResult = OzLivenessSDK.runOnDeviceLivenessAnalysis(mediaList)

6.3.3

• Liveness now goes smoother.

• Fixed freezes on Xiaomi devices.

• Optimized image converting.

6.3.1

• New metadata parameter for OzLivenessSDK.uploadMedia and new OzLivenessSDK.uploadMediaAndAnalyze method to pass this parameter to folders.

6.2.8

• Added functions for SDK initialization with LicenseSources: LicenseSource.LicenseAssetId and LicenseSource.LicenseFilePath. Use the OzLivenessSDK.init method to start initialization.

• Now you can get the license info upon initialization val licensePayload = OzLivenessSDK.getLicensePayload().

6.2.4

• Added the Kyrgyz locale.

6.2.0

• Added local analysis functions.

• You can now configure the face frame.

• Fixed version number at the Liveness screen.

6.1.0

• Added the main camera support.

6.0.1

• Added configuration from license support.

6.0.0

• Added the OneShot gesture.

• Added new states for OzAnalysisResult.Resolution.

• Added the uploadMediaAndAnalyze method to load a bunch of media to the server at once and send them to analysis immediately.

• OzMedia is renamed to OzAbstractMedia and got subclasses for images and videos.

• Fixed camera bugs for some devices.

5.1.0

• Access token updates automatically.

• Renamed accessToken to permanentAccessToken.

• Added R8 rules.

• Configuration became easier: config settings are mutable.

5.0.2

• Fixed the oval frame.

• Removed the unusable parameters from AnalyseRequest.

• Removed default attempt limits.

5.0.0

• To customize the configuration options, the config property is added instead of baseURL, accessToken, etc. Use OzConfig.Builder for initialization.

• Added license support. Licences should be installed as raw resources. To pass them to OzConfig, use setLicenseResourceId.

• Replaced the context-dependent methods with analogs.

• Improved the image analysis.

• Removed unusable dependencies.

• Fixed logging.

To connect SDK to Oz API, specify the API URL and access token as shown below.

OZSDK.setApiConnection(Connection.fromServiceToken(host: "https://sandbox.ohio.ozforensics.com", token: token)) { (token, error) in
}

Alternatively, you can use the login and password provided by your Oz Forensics account manager:

OZSDK.setApiConnection(Connection.fromCredentials(host: “https://sandbox.ohio.ozforensics.com”, login: login, password: p)) { (token, error) in
    // Your code to handle error or token
}

By default, logs are saved along with the analyses' data. If you need to keep the logs distinct from the analysis data, set up the separate connection for telemetry as shown below:

let eventsConnection = Connection.fromCredentials(host: https://tm.ozforensics.com/,
                                login: <your_telemetry_user_eg_tm@company.com>,
                                password: your_telemetry_password)
OZSDK.setEventsConnection(eventsConnection) { (token, error) in
}

If you want to get back to the previous (up to 6.4.2) versions' design, reset the customization settings of the capture screen and apply the parameters that are listed below.

OzLivenessSDK.config.customization = UICustomization(
    // customization parameters for the toolbar
    toolbarCustomization = ToolbarCustomization(
        closeIconTint = Color.ColorHex("#FFFFFF"),
        backgroundColor = Color.ColorHex("#000000"),
        backgroundAlpha = 100,
    ),
    // customization parameters for the center hint
    centerHintCustomization = CenterHintCustomization(
        verticalPosition = 70
    ),
    // customization parameters for the hint animation
    new HintAnimation(
        hideAnimation = true
    ),
    // customization parameters for the frame around the user face
    faceFrameCustomization = FaceFrameCustomization(
        strokeDefaultColor = Color.ColorHex("#EC574B"),
        strokeFaceInFrameColor = Color.ColorHex("#00FF00"),
        strokeWidth = 6,
    ),
    // customization parameters for the background outside the frame
    backgroundCustomization = BackgroundCustomization(
        backgroundAlpha = 100
    ),
)

OzLivenessSDK.INSTANCE.getConfig().setCustomization(new UICustomization(
// customization parameters for the toolbar
new ToolbarCustomization(
    R.drawable.ib_close,
    new Color.ColorHex("#FFFFFF"),
    new Color.ColorHex("#000000"),
    100, // toolbar text opacity (in %)
    ),
// customization parameters for the center hint
new CenterHintCustomization(
    70, // vertical position (in %)
),
// customization parameters for the hint animation
new HintAnimation(
    true, // hide animation
),
// customization parameters for the frame around the user face
new FaceFrameCustomization(     
    new Color.ColorHex("#EC574B"), 
    new Color.ColorHex("#00FF00"),
    6, // frame stroke width (in dp)
 ),
// customization parameters for the background outside the frame
new BackgroundCustomization(
    100 // background opacity (in %)
),
  )
);

Master license is the offline license that allows using Mobile SDKs with any bundle_id, unlike the regular licenses. To get a master license, create a pair of keys as shown below. Email us the public key, and we will email you the master license shortly after that. Your application needs to sign its bundle_id with the private key, and the Mobile SDK checks the signature using the public key from the master license. Master licenses are time-limited.

Generating Keys

This section describes the process of creating your private and public keys.

Creating a Private Key

To create a private key, run the commands below one by one.

openssl genpkey -algorithm RSA -outform DER -out privateKey.der -pkeyopt rsa_keygen_bits:2048
# for MacOS
base64 -i privateKey.der -o privateKey.txt
# for Linux 
base64 -w 0 privateKey.der > privateKey.txt

You will get these files:

• privateKey.der is a private .der key;

• privateKey.txt is privateKey.der encoded by base64. This key containing will be used as the host app bundle_id signature.

File examples:

The OpenSSL command specification: https://www.openssl.org/docs/man1.1.1/man1/openssl-pkcs8.html

Creating a Public Key

To create a public key, run this command.

openssl rsa -pubout -in privateKey.der -out publicKey.pub

You will get the public key file: publicKey.pub. To get a license, please email us this file. We will email you the license.

File example:

SDK Integration

SDK initialization:

OZSDK(licenseSources: [LicenseSource], masterLicenseSignature: String? = nil, completion: @escaping ((LicenseData?, LicenseError?) -> Void))

License setting:

setLicense(licenseSource: LicenseSource, masterLicenseSignature: String? = nil)

Prior to the SDK initializing, create a base64-encoded signature for the host app bundle_id using the private key.

Signature creation example:

private func getSignature() -> String? {
    let privateKeyBase64String = "the string copied from the privateKey.txt file"
    // with key example:
    // let privateKeyBase64String = "MIIEogIBAAKCAQEAvxpyONpif2AjXiiG8fs9pQkn5C9yfiP0lD95Z0UF84t0Ox1S5U1UuVE5kkTYYGvS2Wm7ykUEGuHhqt/PyOAxrrNkAGz3OcVTsvcqPmwcf4UNdYZmug6EnQ5ok9wxYARS0aYqJUdzUb4dKOYal6WpHZE4yLx08R0zQ5jPkg5asT2u2PLB7JHZNnXwBcvdUonAgocNzdakUbWTNHKMxjwdAvwdIICdIneLZ9nCqe1d0cx7JBIhLzSPu/DVRANF+DOsE9JM8DT/Snnjok2xXzqpxBs1GwqiMJh98KYP78AVRWFuq3qbq0hWpjbq+mWl8xa7UMv8WxVd4PvQkWVYq/ojJwIDAQABAoIBAEvkydXwTMu/N2yOdcEmAP5I25HQkgysZNZ3OtSbYdit2lQbui8cffg23MFNHA125L65Mf4LWK0AZenBhriE6NYzohRVMf28cxgQ9rLhppOyGH1DCgr79wiUj02hVe6G6Qkfj39Ml+yvrs7uS0NMZBQ89yspRNv4t8IxrsWXc8cNQr33fdArlZ021Z12u2wdamaagiFwTa6ZYcQ5OYl3d/xL+oAwf9ywHwRrVM2JksGCxrcLJ7JCOL6lLyjp8rRrIG4iZ1V8YDfUNHmwD4w1fl30H6ejA+Cy5qge7CBZK+hqKr+hOcfBfakfOtgcEbFq2L8DqHoSaTeY6n9wjPJiFrkCgYEA8fc/Cg+d0BN98aON80TNT+XLEZxXMH+8qdmJYe/LB2EckBj1N0en87OEhqMFm9BjYswGf/uO+q2kryEat1n3nejbENN9XaO36ahlXTpQ6gdHO3TuO+hnnUkXeUNgiGYs+1L8Ot6PuNykwL0BZ09U0iBVoawEjTAg9tLNfVW2upsCgYEAyi/75YFT3ApxfSf/9XR74a0aKrfGGlBppcGvxuhVUC2aW2fPEZGXo4qlEhP2tyVTfj78F2p0Fnf3NSyvLZAzSwKo4w8EyZfXn1RI4sM95kzIMhH3Gz8VxCZWKEgr7cKNU5Zhs8un/VFd9Mc0KyZfmVy4VrZ5JumgahBRzSn9zGUCgYA7TTt3/cfRvVU6qbkajBw9nrYcRNLhogzdG+GdzSVXU6eqcVN4DunMwoySatXvEC2rgxF8wGyUZ4ZbHaPsl/ImE3HNN+gb0Qo8C/d719UI5mvA2LGioRzz4XwNTkQUaeZQWlBTJUTYK8t9KVV0um6xaRdTnlMnP0p088lFFILKTQKBgDsR98selKyF1JBXPl2s8YCGfU2bsWIAukz2IG/BcyNgn2czFfkxCxd5qy5z7LGnUxRgPHBu5oml9PBxJKDwLzwsA8GKosBu/00KZ9zwY8ZECn0uaH5qWOacuLE+HK9zFq0kE1lfF65XtlaMWH5+0JFS2HxlBVJMEVTLfcquCPtNAoGAG6ytPm24AS1satPwlKnZODQEg0kc7d5S42jbt4X7lwICY/7gORSdbNS8OmrqYhP/8tDOAUtzPQ20fEt43/VA87bq88BVzoSp4GVQcSL44MzRBQHQwTVkoVnbCXSD9K9gZ71wii+m+8rZZ0EMdiTR3hsRXRuSmw4t8y3CuzlZ9k4="
    guard let data = Data(base64Encoded: privateKeyBase64String, options: [.ignoreUnknownCharacters]) else {
      return nil
    }
     
    let sizeInBits = data.count * 8
    let keyDict: [CFString: Any] = [
      kSecAttrKeyType: kSecAttrKeyTypeRSA,
      kSecAttrKeyClass: kSecAttrKeyClassPrivate,
      kSecAttrKeySizeInBits: NSNumber(value: sizeInBits)
    ]
     
    var error: Unmanaged<CFError>?
    guard let secKey = SecKeyCreateWithData(data as CFData, keyDict as CFDictionary, &error) else {
      return nil
    }
     
    guard let bundleID = Bundle.main.bundleIdentifier else {
      return nil
    }
    guard let signature = SecKeyCreateSignature(secKey,
                          .rsaSignatureMessagePKCS1v15SHA512,
                          Data(bundleID.utf8) as CFData,
                          &error) else {
      return nil
    }
    return (signature as Data).base64EncodedString()
  }

Pass the signature as the masterLicenseSignature parameter either during the SDK initialization or license setting.

If the signature is invalid, the initialization continues as usual: the SDK checks the list of bundle_id included into the license like it does it by default without a master license.

If you want to get back to the previous (up to 6.4.2) versions' design, reset the customization settings of the capture screen and apply the parameters that are listed below.

Create a controller that will capture videos as follows:

Once video is captured, the system calls the onOZLivenessResult method:

If a user closes the capturing screen manually, the failedBecauseUserCancelled error appears.

License

1. Rename this file to forensics.license and put it into the project. In this case, you don't need to set the path to the license.

2. During the runtime: when initializing SDK, use the following method.

or

LicenseSource a source of license, and LicenseData is the information about your license. Please note: this method checks whether you have an active license or not and if yes, this license won't be replaced with a new one. To force the license replacement, use the setLicense method.

In case of any license errors, the system will use your error handling code as shown above. Otherwise, the system will return information about license. To check the license data manually, use OZSDK.licenseData.

Possible License Errors

If you use our SDK just for capturing videos, omit this step.

To check liveness and face biometry, you need to upload media to our system and then analyze them.

Below, you'll see the example of performing a check and its description.

To delete media files after the checks are finished, use the cleanTempDirectory method.

Adding Metadata

To add metadata to a folder, use AnalysisRequest.addFolderMeta.

Extracting the Best Shot

In the params field of the Analysis structure, you can pass any additional parameters (key + value), for instance, to extract the best shot on the server side.

Using Media from Another SDK

Adding Media to a Certain Folder

If you want to add your media to the existing folder, use the addFolderId method:

In this section, we explain how to use Oz Flutter SDK for iOS and Android.

Before you start, it is recommended that you install:

• Flutter 3.0.0 or higher;

• Android SDK 21 or higher;

• dart 2.18.6 or higher;

• iOS platform 13 or higher;

• Xcode.

8.16.0 – Mar. 11, 2025

• Updated the authorization logic.

• Improved voiceover.

• SDK now compresses videos if their size exceeds 10 MB.

• Head movement gestures are now handled properly.

• Security updates.

8.15.0 – Dec. 30, 2024

• Changed the wording for the head_down gesture: the new wording is “tilt down”.

• Added proper focus order for VoiceOver when the antiscam hint is enabled.

• Added the public setting extract_action_shot in the Demo Application.

• Bug fixes.

• Security updates.

8.14.0 – Dec. 3, 2024

• Accessibility updates according to WCAG requirements: the SDK hints and UI controls can be voiced.

• Improved user experience with head movement gestures.

• Minor bug fixes and telemetry updates.

8.13.0 – Nov. 11, 2024

• The screen brightness no longer changes when the rear camera is used.

• Fixed the video recording issues on some smartphone models.

• Security and telemetry updates.

8.12.2 – Oct. 24, 2024

• Internal SDK improvements.

8.12.1 – Sept. 30, 2024

• Added Xcode 16 support.

• Security and telemetry updates.

8.11.0 – Sept. 10, 2024

• Security updates.

8.10.1 – Aug. 23, 2024

• Bug fixes.

8.10.0 – Aug. 1, 2024

• SDK now requires Xcode 15 and higher.

• Security updates.

• Bug fixes.

8.9.1 – July 16, 2024

• Internal SDK improvements.

8.8.3 – July 11, 2024

• Internal SDK improvements.

8.8.2 – June 25, 2024

• Bug fixes.

8.8.1 – June 25, 2024

• Logging updates.

8.8.0 – June 18, 2024

• Security updates.

8.7.0 – May 10, 2024

• Added a description for the error that occurs when providing an empty string as an ID in the addFolderID method.

• Bug fixes.

8.6.0 – Apr. 10, 2024

• The messages displayed by the SDK after uploading media have been synchronized with Android.

• The bug causing analysis delays that might have occurred for the One Shot gesture has been fixed.

8.5.0 – Mar. 06, 2024

• Removed the pause after the Scan gesture.

• Security and logging updates.

8.4.2 – Jan. 24, 2024

• Security updates.

8.4.0 – Jan. 09, 2024

• Changed the default behavior in case a localization key is missing: now the English string value is displayed instead of a key.

• Fixed some bugs.

8.3.3 – Dec. 11, 2023

• Internal licensing improvements.

8.3.0 – Nov. 17, 2023

• Implemented the possibility of using a master license that works with any bundle_id.

• Fixed the bug with background color flashing.

8.2.1 – Nov. 11, 2023

• Bug fixes.

8.2.0 – Oct. 30, 2023

• The Analysis structure now contains the sizeReductionStrategy field. This field defines what type of media is being sent to the server in case of the hybrid analysis once the on-device analysis is finished successfully.

• The messages for the errors that are retrieved from API are now detailed.

• The toFrameGradientColor option in hintAnimationCustomization is now deprecated, please use the hintGradientColor option instead.

• Got back the iOS 11 support.

8.1.1 – Oct. 09, 2023

8.1.0 – Sept. 07, 2023

• Updated the Liveness on-device model.

• Added the Portuguese (Brazilian) locale.

• If a media hasn't been uploaded correctly, the system now repeats the upload.

• Added a new method to retrieve the telemetry (logging) identifier: getEventSessionId.

• The setPermanentAccessToken, configure and login methods are now deprecated. Please use the setApiConnection method instead.

• The setLicense(from path:String) method is now deprecated. Please use the setLicense(licenseSource: LicenseSource) method instead.

• Fixed some bugs and improved the SDK work.

8.0.2 – Aug. 15, 2023

• Fixed some bugs and improved the SDK algorithms.

8.0.0 – June 27, 2023

• Added the new analysis mode – hybrid (Liveness only). If the score received from an on-device analysis is too high, the system initiates a server-based analysis as an additional check.

• Improved the on-device models.

• Updated the run method.

• Added new structures: RequestStatus (analysis state), ResultMedia (analysis result for a single media) and RequestResult (consolidated analysis result for all media).

• The updated AnalysisResult structure should be now used instead of OzAnalysisResult.

• For the OZMedia object, you can now specify additional tags that are not included into our tags list.

• The Selfie video length is now about 0.7 sec, the file size and upload time are reduced.

• The hint text width can now exceed the frame width (when using the main camera).

• The methods below are no longer supported:

7.3.0 – June 06, 2023

• Added the center hint background customization.

• Added new face frame forms (Circle, Square).

• Synchronized the default customization values with Android.

• Added the Spanish locale.

• iOS 11 is no longer supported, the minimal required version is 12.

7.2.1 – May 24, 2023

• Fixed the issue with the server-based One shot analysis.

7.2.0 – May 18, 2023

• Improved the SDK algorithms.

7.1.6 – May 04, 2023

• Fixed error handling when uploading a file to API. From this version, an error will be raised to a host application in case of an error during file upload.

7.1.5 – Apr. 03, 2023

• Improved the on-device Liveness.

7.1.4 – Mar. 24, 2023

• Fixed the animation for sunglasses/mask.

• Fixed the bug with the .document analysis.

• Updated the descriptions of customization methods and structures.

7.1.2 – Feb. 21, 2023

• Updated the TensorFlow version to 2.11.

• Fixed several bugs, including the Biometry check failures on some phone models.

7.1.1 – Feb. 06, 2023

• Added customization for the hint animation.

7.1.0 – Jan. 20, 2023

• Integrated a new model.

• Added the uploadMedia method to AnalysisRequest. The addMedia method is now deprecated.

• Fixed the combo analysis error.

• Added a button to reset the SDK theme and language settings.

• Fixed some bugs and localization issues.

• Extended the network request timeout to 90 sec.

• Added a setting for the animation icon size.

7.0.0 – Dec. 08, 2022

6.7.0

6.4.0

• Synchronized the version numbers with Android SDK.

• Added a new field to the Analysis structure. The params field is for any additional parameters, for instance, if you need to set extracting the best shot on server to true. The best shot algorithm chooses the most high-quality frame from a video.

• Fixed some localization issues.

• Changed the Combo gesture.

• Now you can launch the Liveness check to analyze images taken with another SDK.

3.0.1

• The Zoom in and Zoom out gestures are no longer supported.

3.0.0

• Added a new simplified analysis structure – AnalysisRequest.

2.3.0

• Added methods of on-device analysis: runOnDeviceLivenessAnalysis and runOnDeviceBiometryAnalysis.

• You can choose the installation version. Standard installation gives access to full functionality. The core version (OzLivenessSDK/Core) installs SDK without the on-device functionality.

• Added a method to upload data to server and start analyzing it immediately: uploadAndAnalyse.

• Improved the licensing process, now you can add a license when initializing SDK: OZSDK(licenseSources: [LicenseSource], completion: @escaping ((LicenseData?, LicenseError?) -> Void)), where LicenseSource is a path to physical location of your license, LicenseData contains the license information.

• Added the setLicense method to force license adding.

2.2.3

• Added the Turkish locale.

2.2.1

• Added the Kyrgyz locale.

• Added Completion Handler for analysis results.

• Added Error User Info to telemetry to show detailed info in case of an analysis error.

2.2.0

• Added local on-device analysis.

• Added oval and rectangular frames.

• Added Xcode 12.5.1+ support.

2.1.4

• Added SDK configuration with licenses.

2.1.3

• Added the One Shot gesture.

• Improved OZVerificationResult: added bestShotURL which contains the best shot image and preferredMediaURL which contains an URL to the best quality video.

• When performing a local check, you can now choose a main or back camera.

2.1.2

• Authorization sessions extend automatically.

• Updated authorization interfaces.

2.1.1

• Added the Kazakh locale.

• Added license error texts.

2.1.0

• You can cancel network requests.

• You can specify Bundle for license.

• Added analysis parameterization documentAnalyse.

• Fixed building errors (Xcode 12.4 / Cocoapods 1.10.1).

2.0.0

• Added license support.

• Added Xcode 12 support instead of 11.

• Fixed the documentAnalyse error where you had to fill analyseStates to launch the analysis.

• Fixed logging.

Please note: this feature has been implemented in 8.1.0.

To add or update the language pack for Oz iOS SDK, use the set(languageBundle: Bundle) method. It shows the SDK that you are going to use the non-standard bundle. In OzLocalizationCode, use the custom language (optional).

• If you don’t set the custom language and bundle, the SDK uses the pre-installed languages only.

• If the custom bundle is set (and language is not), it has a priority when checking translations, i.e, SDK checks for the localization record in the custom bundle localization file. If the key is not found in the custom bundle, the standard bundle text for this key is used.

• If both custom bundle and language are set, SDK retrieves all the translations from the custom bundle localization file.

A list of keys for iOS:

The keys Action.*.Task refer to the appropriate gestures. Others refer to the hints for any gesture, info messages, or errors.

When new keys appear with new versions, if no translation is provided by your custom bundle localization file, you’ll see the default (English) text.