Skip to content

Frequently Asked Questions (FAQ)

Jump to bottom
Nedas Matulevičius edited this page Jun 9, 2026 · 1 revision

Under this section you will find the most commonly occurring issues when integrating or running the SDK from the client application. Feel free to explore the options offered here, and if there are some missing questions, you can ask here by commenting or writing the email directly to Ondato support team at support@ondato.com

Q1: I'm getting the "this feature is not included inside build.gradle file" crash during runtime. What should I do?

This happens due to the misconfiguration between the setup created in the Admin Centre, which essentially passes down the config to the backend services, and the included dependencies inside the client application. While sdk-core module is mandatory in all cases, all other modules are by design optional and can be skipped. However, if your business cases requires one or more of the following:

  • NFC tag scanning of the documents
  • Device screen recording with audio and video recording
  • Automatic document capture with the help of AI

then you will need to include the optional modules based on the features you use.

The optional modules are these:

  • nfc-reader - this module is necessary if you're planning to use NFC tag scanning technology from passports and ID cards.
  • screen-recorder - this module is necessary if you're planning to capture end user's actions during the identification process on the device. Note that both video and audio feeds are recorded during the flow.
  • document-autoresolver - this module is necessary if your setup has automatic document capture enabled. This is true for the vast majority of cases, so check accordingly if your setup has this feature enabled or disabled.

Q2: Why I'm not able to start the identification even if I generated the identification ID correctly?

In this scenario, it is highly recommended to check against which environment (sandbox or production) the identification ID was created and on which environment the SDK is being launched. The ID and the SDK environments must match in order to launch the process successfully.

Q3: The screen recording shows dark screen when the end user goes through the face scanning process. Why is this the case?

This is mostly due to the fact that active liveness is a 3rd party process on which we have limited control, and that 3rd party explicitly states that during the face scan process, the screen recording ability is protected, therefore the device shows dark screen instead of the actual UI. The end user, however, sees everything as usual.

If your configuration has passive liveness enabled, then the screen recording functionality will record the actions when the end user tries to scan their face and it will be recorded by the SDK.

Q4: What is this new sdk module and how should I use it?

This new module is created starting with version 3.5.0 and it is a fused library, meaning that it contains other libraries bundled together into a single AAR file, previously known as FAT AAR. sdk module contains two other packages:

  • sdk-core, which is the core Ondato SDK package, without which no other optional modules would work and the standard flows could not be started also,
  • document-autoresolver, which is the automatic document capture package. Technically speaking, this package is optional to have, but since most of the clients would have automatic document capture enabled on other services (e.g. Web IDV solution), this convenience package would help integrating the solution as one dependency into the clients' mobile applications.

Note that sdk contains both sdk-core and document-autoresolver, meaning that these packages do not need to be added separately as dependencies in your app. If you want to use nfc-reader or screen-recorder packages, though, these need to be included as separate dependencies as it was before.

Clone this wiki locally