This is a release of the OneSpan Threat View Client SDK with issue fixes.
Product package
The OneSpan Threat View Client SDK package contains the following:
Threat View Client SDK:
onespan_threat_view_client-SDK_version.zip
Contains the relevant libraries for SDK integration. For details about the package contents, see Threat View Client SDK Integration Guide: Product package.
onespan-threat_view_client-SDK_version_checksums.txt
Text file with the checksums for product verification.
For information about the installation of Threat View, see Installation Guide. For information about the SDK integration, see Integration of the Onespan Threat View Client SDK and the technical documentation contained in the SDK product package.
Supported platform versions
The Threat View Client SDK supports the following platforms:
Android | iOS |
|---|---|
Minimum: Android 7 (API level 24) | Minimum: iOS 15 or later |
Target: Android 15 (API level 35) | Swift: 5 or later |
Kotlin: 1.9.0 or later | Xcode: 16 or later |
AGP: 8.10.0 or later | |
Target SDK: 36 | |
Proguard: Consumer rules are automatically applied from the SDK artifact—no additional configuration required. | |
OneSpan Mobile Application Shielding: 7.4.2 or later The final APK must be shielded using the Shielding Tool to enable Threat View to collect threats, report them back to the platform, and enforce runtime integrity checks to prevent tampering. |
Fixes and other changes
Client SDK failed to send events
Description: On Android, the Threat View Client SDK failed to send events to the Threat View back end. This happened when the device, where the SDK was integrated, used a non-UTC time zone, thus lacking the potential GMT offset based on the location of the device. The reason for the failure to send data was that the back end expected the time to be sent in GMT format (GMT±HH:MM) which was different than the format reported by the SDK.
Status: This issue has been fixed. The SDK now correctly reports the device's current timezone, indicating the timezone offset (e.g., GMT+05:30, GMT-08:00), and including adjustments for daylight saving times. The SDK now complies with the requirements for back-end validation on all supported Android API levels: for devices running Android API level 26 or later, the SDK relies on the Java 8 Date-Time API, while it falls back to manual offset of GMT +00:00 for devices running Android API level 25 or earlier.
Third party licenses and open source software
For information about third party software notices used in this product, see the relevant files in the product package:
integration.md: "Dependencies (Detailed Listing)" for the Threat View Client SDK.