Android Trust SDK Release Notes

The Daon Trust SDK is an Android mobile SDK that allows developers to embed a fully realized authentication and identity proofing journey into their mobile apps. The Trust SDK is managed by the TrustX platform to collect Appkeys, device, face, document, and NFC data to conduct an authentication or onboarding flow.

Trust SDK Size Report

The table below contains the universal binary sizes based on building a basic application with a specific feature supported.

The basic application size without frameworks is 27 KB when compressed and 111 KB when uncompressed.

Daon Trust SDK v1.8.18

Release Date: April 2026

Improvements

Device Integrity Module

A new Device Integrity module has been added to the Trust SDK. This module integrates with Device Integrity Signals to provide device intelligence capabilities, enabling the collection of device signals that can be used for fraud detection and risk assessment during onboarding flows. The module is available as a separate optional dependency (trust-deviceintegrity) so it can be included only when needed.

Push Notification Support

The SDK now supports receiving and handling push notifications as part of authentication and onboarding flows. Integrators can configure push notification delivery through the existing Trust SDK setup, allowing users to receive step-up or approval prompts without leaving the application.

Configurable Exit Confirmation Dialog

A new optional parameter, showExitConfirmationDialog, has been added to DaonOptions. When set to true, the SDK will display a confirmation dialog when the user attempts to exit an active onboarding session, preventing accidental exits. By default this is set to false, preserving existing behavior.

Centralized Permission Handling

A new PermissionHelper utility class has been added to simplify runtime permission management. It provides a unified API for requesting one or more permissions at once and receiving results through a callback, reducing boilerplate in host applications that need to request camera, NFC, or notification permissions as part of a Trust SDK flow.

Maven Repository Handling

The Daon Trust SDK is now available as a standard Maven dependency. You can add it directly to your project by declaring the Daon Maven repository and adding the SDK as a dependency — no additional setup or manual file management is required. This makes it easier to keep the SDK up to date and simplifies integration into new projects.

Dependency Version Catalog

All third-party library versions used by the SDK are now managed through a centralised Gradle version catalog (gradle/libs.versions.toml). Instead of hardcoding version strings scattered across individual build.gradle files, all versions are declared once in the catalog and referenced by alias throughout the project.

To use the version catalog in your own project, declare it in your settings.gradle:

xxxxxxxxxx

dependencyResolutionManagement {

    versionCatalogs {

        libs {

            from(files("gradle/libs.versions.toml"))

        }

    }

}

You can then reference any library or version by its alias in your build.gradle:

xxxxxxxxxx

dependencies {

    implementation libs.androidx.appcompat

    implementation libs.daon.trust

    implementation libs.daon.trust.deviceintegrity

}

This approach makes it easy to audit and update dependency versions in a single place, and ensures consistency across all modules in the project.

Breaking API Changes

• The signature of ITrustXJSWebToNative.onOperation() has changed. The second parameter type has been updated from IDaonConfiguration? to String. Any application that implements this interface must update the method signature accordingly, otherwise the project will not compile.

Before:

xxxxxxxxxx

fun onOperation(operation: String, configData: IDaonConfiguration?)

After:

xxxxxxxxxx

fun onOperation(operation: String, configData: String)

Minor API Changes

• New method DaonTrustSDK.addDeviceIntegrityManager(manager: IDeviceIntegrityManager) added. Register an instance of IDeviceIntegrityManager to enable Device Integrity capabilities within the Trust SDK flow.
• New class DaonDIConfiguration added. Holds the configuration required by the Device Integrity module (apiKey, region, endpoint).
• New interface IDeviceIntegrityManager added. Implement this interface to provide a custom Device Integrity manager to the SDK.
• New class PermissionHelper added. Utility for requesting one or more runtime permissions and receiving results via the PermissionHelper.PermissionRequestListener callback interface.
• New optional field showExitConfirmationDialog: Boolean added to DaonOptions (default: false). Set to true to show a confirmation dialog when the user attempts to exit an active session.
• New field deviceIntegrityModule: DaonTrustModule? added to DaonTrustModules. Reflects whether the Device Integrity module is included in the capabilities returned by the SDK.

Bug Fixes

Library Updates

Daon Trust SDK v1.7.5

Release Date: January 2026

In this version of the Trust SDK, improvements have been implemented to enhance overall stability and reliability of the SDK. Identified memory management issues, including memory leaks present in previous versions, have been resolved.

Additionally, a new feature has been introduced - Appkeys support - extending the capabilities for authenticator registration and authentication via the FIDO protocol within Trust SDK.

What's New

Appkeys Support

Added support for Appkeys. This is an optional feature of the Trust SDK and can provide:

1. Registration of biometric and silent authenticators
2. Authentication using a previously registered authenticator
3. Authenticator deregistration

To integrate with Appkeys, follow the integration guide outlined in Android Trust SDK Integration section.

Bug Fixes

Library Updates

The libraries listed below are added and only necessary when implementing the optional Appkeys integration.

Added AAR Libraries

• com.daon.sdk.authenticator-5.0.79.aar
• com.daon.sdk.crypto-4.9.10.aar
• com.daon.sdk.device-4.9.8.aar
• com.daon.sdk.fido.client-ktx-5.0.79.aar

Firebase:

• com.google.firebase:firebase-bom:34.5.0
• com.google.firebase:firebase-analytics
• com.google.firebase:firebase-common
• com.google.firebase:firebase-messaging
• Added google-service.json to the sample app
  • The google-services.json file has been added to the sample application, as it is currently required for Appkeys functionality. This will be fixed in the next release.

Manifest Changes

android:allowBackup is set to false by default to match the setting required if using Appkeys.

General SDK Gradle Changes

Daon Trust SDK v1.6.2

Release Date: September 2025

Improvements

Implemented additional checks for the provided URL

Added additional checks to ensure that the server URL parameter provided to the Trust SDK is valid and correctly formatted in order to guarantee that the application gets the correct response from the SDK.

Improved the whitelist check error handling

Updated the error codes returned during the whitelist check, to ensure that any issues that may occur during the check are as clear as possible. Hence, we are now returning the NO_INTERNET_CONNECTION error code instead of URL_NOT_WHITELISTED if there has been a problem with the connection and not a problem reported by a whitelisting service.

Fix missing build number

The Trust SDK version is now reported in full format (major.minor.build). Previously, the build number was missing from the version string.

Exposed information when the back action button is pressed

We are now returning the information when the back action button is pressed, through the onInfo() API call. Each time a back action button is pressed, the Trust SDK will return the BACK_BUTTON_PRESSED status code in the onInfo() callback.

NOTE: Since we are now using the onInfo() callback to return this information, it is no longer deprecated.

Breaking API Changes

Added parameter into the onSuccess() API call

Added a String parameter into the onSuccess() API call, which is overridden from the DaonEventListener class. This parameter is a message from the WebApp and it carries information about the status of the onboarding submission. This message is provided by the WebApp and returned by the Trust SDK, therefore it does not represent any status from the Trust SDK itself.

Minor API Changes

Added new API call - stop()

Implemented a new stop() API call which will serve the purpose to manually stop the Trust SDK processes.

NOTE: This call does not guarantee the interruption of the WebApp session right away, it just interrupts the Trust SDK process and returns the appropriate error code (SDK_STOPPED_PROGRAMMATICALLY)

Bug Fixes

Daon Trust SDK v1.5.34

What's Changed

• Updated NFC SDK to v1.2.38. The app can now be installed on devices that lack NFC hardware support.

Daon Trust SDK v1.5.31

Release Date: January 2025

Improvements

• Added support for NFC scanning in TrustX Onboarding process. A new module designed to support NFC document chip scanning, data reading/parsing and sending it to the WebApp. This new NFC support includes:

  • Checks for NFC sensor availability on the device
  • Checks indicating if NFC sensor on the device is enabled/disabled
  • Reading and parsing of all supported data groups present on the passport NFC chip

• Upgraded SDK to support Android 15. The targetSdk and compileSdk have been updated to the latest version 35, meaning that Android devices running with Android 15 OS version are now supported. The Trust SDK is compatible with the latest 16KB page size changes that Android 15 introduced.

Breaking API Changes

Changes regarding DaonOptions parameter default values

The default value of the statusBarColor parameter has changed to null. This way, if the new value is not provided, the SDK will use the default value set internally.

Changes regarding model classes (transition from Serializable to Parcelable data types)

Three Model classes have been updated to Parcelable data types, mainly to improve performances for the SDK and to make object parsing easier.

Affected classes are DaonOptions, DaonEvent, DaonOptions.

Changes regarding targetSdk and compileSdk upgrade to latest API level 35

As the Trust SDK has been upgraded to support the latest Android 15 features, the SDK now requires that integrating applications also supports API level 35. Without this upgrade, some of the new features brought by Android API level 35 (e.g. EdgeToEdge) that are implemented in the Trust SDK will not function properly.

Minor API Changes

Added new NFC analytics events

New NFC analytics events have been added that are used to better indicate the current stage of the NFC processing activity. New events are:

• NFC_INPUT_PARSING_ERROR - triggered when NFC configuration payload sent by WebApp could not be parsed
• NFC_BACKGROUND_CANCELED - triggered when NFC scanning process has been canceled due to application going in the background

Bug Fixes

Library Updates

• NFC SDK v1.2.33
• Trust NFC Manager v1.5.31