Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Release notes and FAQ

Risk Management mobile SDK release notes

search

Please Note:

Risk Management mobile SDK release notes

Release information

Release name: Risk Management SDK 3.1.0

Release date: Mar 28, 2024

Supported platforms

  • Android 7.0 and later
  • iOS 14.0 and later

Supported processor architectures

  • armeabi-v7a, arm64-v8a, x86 and x86_64

Updates

  • Integrated new TMX SDK v7.6.x

Release name: Risk Management SDK 3.0.0

Release date: Apr 18, 2024

Supported platforms

  • Android 7.0 to 14.0
  • iOS 14.0 to 18.0

Supported processor architectures

  • armeabi-v7a, arm64-v8a, x86 and x86_64

Updates

Integrated new TMX SDK v7.3.x

Initialize the TMX SDK to use Thales visitID as session ID

iOS: Repackage SDK as dynamic framework with privacy manifest file

Fixed issues and bugs

  • Fix duplicated TMX session ID

Release name: Risk Management SDK 2.8.1

Release date: Mar 22, 2024

Supported platforms

  • Android 7.0 and later.

Supported processor architectures

  • armeabi-v7a, arm64-v8a, x86 and x86_64

Updates

  • NA

Fixed issues and bugs

  • Fixed the crash on prefetch during location updates.

Known limitations

  • For ThreatMetrix signals collection, before calling requestVisitID(), the app has to call the startPrefetchSignals() method and then wait for requestPrefetchStatus(GAHResponseCallback to complete. Otherwise, an error code of 500 is returned in the signal collection of requestVisitID().

  • The BehavioSec signal is used to monitor short text inputs such as username and password. If the timing data of the BehavioSec signal group exceeds 512KB from a long text input, a status code of 403-Forbidden error is returned by the Risk Management back end.

  • The SDK initialization does not work without a Wi-Fi or mobile data connection. Hence, signals such as ThreatMetrix cannot be collected until the initialization is done again with the availability of the internet.

Android

  • The countryCode and countryName signals might return errors due to limitations in the Android API. When this occurs, try to collect the signals again.

  • Launcher activity should not extend the BehavioAppCompatActivity.

  • Initialize the BehavioSec SDK before calling any BehavioAppCompatActivity.

BehavioSecCollector collector = BehavioSecCollector.builder().build();
BehavioSecClient.startCollection(collector, application);

Bug-fix tested devices

Android

OS Device
11.0 Motorola Ace 5G
12.0 Google Pixel 3

Release name: Risk Management SDK 2.8.0

Release date: Dec 13, 2023

Supported platforms

  • Android 7.0 and later.
  • iOS 14.0 and later.

Supported processor architectures

  • armeabi-v7a, arm64-v8a, x86 and x86_64

Updates

  • Updated BehavioSec SDK to v3.0.2 (Android) and 3.1.1(iOS) for general stability improvements.

Fixed issues and bugs

  • NA

Known limitations

  • For ThreatMetrix signals collection, before calling requestVisitID(), the app has to call the startPrefetchSignals() method and then wait for requestPrefetchStatus(GAHResponseCallback to complete. Otherwise, an error code of 500 is returned in the signal collection of requestVisitID().

  • The BehavioSec signal is used to monitor short text inputs such as username and password. If the timing data of the BehavioSec signal group exceeds 512KB from a long text input, a status code of 403-Forbidden error is returned by the Risk Management back end.

  • The SDK initialization does not work without a Wi-Fi or mobile data connection. Hence, signals such as ThreatMetrix cannot be collected until the initialization is done again with the availability of the internet.

Android

  • The countryCode and countryName signals might return errors due to limitations in the Android API. When this occurs, try to collect the signals again.

  • Launcher activity should not extend the BehavioAppCompatActivity.

  • Initialize the BehavioSec SDK before calling any BehavioAppCompatActivity.
BehavioSecCollector collector = BehavioSecCollector.builder().build();
BehavioSecClient.startCollection(collector, application);

iOS

  • The isBluetoothEnabled signal of the PlatformSettings signal group is not supported.

Tested devices

Android

OS Device
7.0 Samsung Galaxy J7 Pro
8.0 LG V30+
9.0 Samsung Galaxy S9
10.0 Huawei Mate 40 Pro
11.0 Motorola Ace 5G
12.0 Google Pixel 3a
13.0 One Plue 8
14.0 Pixel 7

iOS

OS Device
14.6 iPhone 7 Plus
15.8 iPhone 6s
16.6.1 iPhone 12 mini
17.1 iPhone 13 mini

SDK compatibilities

In the list of compatibilities for Risk Management SDK version 3.0.0:

X means supported

- means not supported

Operating systems

Platform Version
iOS 14.0 to 18.0
Android 7.0 to 14.0

SDK

Platform SDK
Android from Android SDK 23 to 32

Embedded third-party libraries

Platform third party libraries
iOS ThreatMatrix 7.3
Android ThreatMatrix 7.3-50
Android JNA 5.5.0

Programming languages

Platform Languages Risk Management SDK
iOS Swift X
iOS Objective-C X
Android Java X
Android Kotlin -

Others languages are not supported.

Development platforms

Here is the status on frameworks supported by the Risk Management SDK:

Platform Dev platforms Risk Management SDK
iOS SwiftUI -
Android Jetpack compose X
cross React native -
cross Ionic -
cross Flutter -
cross Cordova planned for Q1-25
cross Xamarin -
cross Mobile Angular UI -

Other development platforms are not supported.

Supported platforms

Depending on the platform you are in, ensure that the following software tools are installed in the development environment:

  • On Android:

    • Android Studio (4.2)
    • Java Development Kit (JDK) version: 1.8.0_152
    • Android SDK

  • On iOS:

    • Xcode (12.4)
    • Objective C (2.0)
    • Swift (4.0)
    • MacOS Catalina 10.15.2 in this version.

On this page