Release notes

Release information

Release name: OIP 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: OIP 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: OIP 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 will be returned in the signal collection of requestVisitID().
• The BehavioSec signal is used to monitor short text input such as username, and password. If the timing data of BehavioSec signal group exceeds 512KB from a long text input, a status code of 403-Forbidden error will be returned by the OIP Risk Management backend.
• 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 internet.

Android

• The countryCode and countryName signals may 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

Release name: OIP 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 will be returned in the signal collection of requestVisitID().
• The BehavioSec signal is used to monitor short text input such as username, and password. If the timing data of BehavioSec signal group exceeds 512KB from a long text input, a status code of 403-Forbidden error will be returned by the OIP Risk Management backend.
• 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 internet.

Android

• The countryCode and countryName signals may 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

iOS