This section lists issues that have not yet been resolved for the current OneSpan Mobile Security Suite version along with possible workarounds, if available.
Biometric Sensor SDK
Platform-specific limitation prevents SDK from detecting changes in biometrics
On Android, the SDK’s biometric change detection APIs (e.g., BiometricManager, BiometricPrompt) can only detect when new fingerprints are added. Detection does not work for removed fingerprints or changes related to face recognition, as Android face sensors are classified as weak biometric authenticators. Biometric change detection, however, only applies to strong authenticators and sensors. This is a platform limitation and the Biometric Sensor SDK inherits this behavior.
Incorrect error code on specific Samsung device
When canceling the fingerprint authentication on the Samsung Galaxy Note 4 Edge (6.0.1), a timeout error code can be randomly returned instead of a cancel error code.
No biometric information prompted on OnePlus devices
On some devices of the OnePlus familly (OnePlus 6T, 7 Pro, 7T, and 7T Pro), in cases where biometric authentication is required, only a fingerprint icon is displayed on screen, no other information. This is due to the native implementation of the biometric prompt API on these devices.
CDDC SDK
Issue to capture SIM identifiers on newer Android versions
Due to tightened platform-level privacy restrictions and limitations introduced by the Original Equipment Manufacturer (OEM), the CDDC SDK does not reliably capture SIM identifiers as of Android 10.
Workaround: Either partner with OEMs or carriers to obtain carrier privileges or rely on non-sensitive metadata such as MCC/MNC (mobile country codes/mobile network codes) or SIM slot count to access SIM identifiers.
Device Binding SDK
Fallback mechanism for Keystore exception
Depending on the OEM and their specific implementation of HARDWARE-backed keystores (Strongbox and TEE), some device models — including devices from Sony, Honor, and other manufacturers — may throw low-level exceptions (mapped to error codes 4409 or 4400) during fingerprint generation using the Hardware options (HARDWARE and/or HARDWARE_WITH_TEE).
The stack trace points to an underlying Keystore exception originating below the application/SDK layer. Since this behavior is tied to the OEM's Strongbox/TEE implementation, it cannot be handled by or worked around from the SDK. This issue is often triggered after a device receives a security or Android update, and may similarly be resolved by a future update, though this cannot be guaranteed.
To mitigate this risk, you can implement a fallback mechanism based on your specific requirements and how you are handling fingerprint continuity and security:
Falling back between
HARDWAREandHARDWARE_WITH_TEE: the fingerprint value remains unchanged.Falling back to
ANDROID_ID(if both hardware options are throwing exceptions): the fingerprint value will be different from the one previously generated.
-4400 Internal error with Samsung S24 Ultra due to StrongBoxUnavailableException
Recently an issue arose that is related to StrongBoxUnavailableException.
Please note that this is not an issue of our SDKs but is caused on the manufacturer's side and outside the control of OneSpan. There is the possibility that this may be fixed automatically in the future.
To provide a fallback mechanism, we have added a new error code, STRONGBOX_UNAVAILABLE and a new fingerprint type, HARDWARE_WITH_TEE.
The recommended flow to generate the fingerprint as follows:
Call the APIs as before by creating the instance using HARDWARE as fingerprint type.
DeviceBinding.createDeviceBinding(context, FingerprintType.HARDWARE).fingerprint(SALT)If this API returns an exception with the error code STRONGBOX_UNAVAILABLE create a new instance with the new fingerprint type HARDWARE_WITH_TEE:
DeviceBinding.createDeviceBinding(context, FingerprintType.HARDWARE_WITH_TEE).fingerprint(SALT)The use of TEE can result in a different fingerprint being generated.
Unexpected termination during Fingerprint generation on specific Android devices
This issue affects devices with the following specifications:
Devices with Mediatek Chipset MT6737 (and variants) running Android 7
Xiaomi Redmi Note 8 Pro devices running Android 11
There is a known issue within Android that prevents the Device Binding SDK from properly generating the fingerprint and causes the system to crash. To resolve the issue, use the ANDROID_ID option to generate the fingerprint, rather than the recommended HARDWARE option.
Unexpected termination on devices running Android 7 using Mediatek chipset with Device Binding SDK
On devices running Android 7 with the Mediatek Chipset MT6737 (and variants), there is a known issue within Android that prevents the Device Binding SDK from properly generating the fingerprint and causes the system to terminate unexpectedly. We recommend upgrading the device to an operating system higher than Android 7, if available. If not, use the ANDROID_ID option to generate the fingerprint.
Device fingerprint issue on Huawei devices with dual SIM
Some Huawei devices offering dual SIM capability expose a dual card management feature in their Settings app to dynamically change the slots of the SIM cards. If this feature is enabled with two SIM cards installed on the mobile device, the Android API can be misled, and return an IMEI which may not correspond to the real IMEI related to the SIM card slot (e.g. request IMEI of the first SIM card slot to Android API, it returns the IMEI of the second SIM card slot). This can cause the generation of an incorrect device fingerprint.
The issue arises when using the getDeviceFingerprint method of the Device Binding SDK.
Device fingerprint migration issue on Huawei devices with dual SIM
Some Huawei devices offering dual SIM capability do not return the same value for the device fingerprint from DIGIPASS for APPS version 4.15.0. This issue is due to an incorrect manufacturer implementation, and has been reproduced on a Huawei P8 Lite (ALE-L21) device.
The issue arises when using the getDeviceFingerprint method of the Device Binding SDK.
Digipass SDK
Migration of dynamic vectors created with SDK 4.0.0 or SDK 4.0.1
Dynamic vectors created with the C API of the Digipass SDK version 4.0.0 or 4.0.1 are rejected by SDK 4.0.2 with an error code –4006 (RETURN_CODE_DYNAMIC_VECTOR_INCORRECT_FORMAT). This error is caused by the extension of the dynamic vector content by three additional bytes. After that extension, the dynamic vector version set in the first byte of the dynamic vector is updated from 0x01 to 0x02.
For dynamic vectors with version 0x01, the workaround consists in re-allocating the dynamic vector with three additional bytes. For more information about migration implementation, refer to the migrateDynamicVector.c file in the sample folder of the C API.
Image Scanner SDK
Inverted QR codes not supported
The scanning of inverted QR codes is not supported. When a QR code with a black or dark background and white QR modules is scanned from an app, the SDK does not detect the QR code. It does not throw an error although it does not scan the image. Only QR codes with white backgrounds and black QR modules are correctly scanned.
SDK returns error with Samsung Galaxy A23
Due to a known issue with the camera on Samsung Galaxy A23, Cronto codes are not decoded properly with the default resolution.
Workaround: The solution to this issue is to increase the resolution using the following code snippet:
var imageAnalysisBuilder = ImageAnalysis.Builder().setTargetRotation(rotation)
// Set Resolution property only for Samsung Galaxy A23 model
if(Build.MANUFACTURER.equals("Samsung", true) && Build.MODEL.contains("A23")) {
imageAnalysisBuilder.setTargetResolution(Size(1080, 1920))
}
imageAnalysisBuilder.build().setAnalyzer(cameraExecutor, QrCodeAnalyzer())Cronto images not properly processed on DOOGEE devices
On certain DOOGEE devices, an issue prevents the from properly scanning and decoding images. Currently, the following devices are reported to be affected:
DOOGEE V Max EEA ( 12)
DOOGEE V30T
DOOGEE S100
Orchestration SDK
Keystore exception
An issue with some device models from Sony, Honor, and other manufacturers causes throwing DeviceBindingSDKException (with error code 4409 or 4400) for the fingerprint generation using the Hardware option (both HARDWARE and HARDWARE_WITH_TEE). The Orchestration SDK catches the exceptions thrown by the dependent SDKs. The stack trace points to an underlying Keystore exception, which cannot be handled from the application side. This issue starts happening after the devices receive an update (either a security update or Android update).
This will cause the storage to be corrupted and the activation will be lost.
Unknown error popup
On devices running Android 12, there is an issue when using the Orchestration SDK code sample with targetSDK:31 . An Unknown error popup displays during the new user registration.
Root Detection SDK
Magisk Hide limitation for root detection with the
If Magisk Hide was used to prevent root detection on an Android device, the SDK is not able to detect that a device is rooted.
Secure Messaging SDK Client
Build error due to changes in SecureMessagingSDKClient.h header
Recent internal changes to the C++ header SecureMessagingSDKClient.h may cause build errors when the header is imported directly. SecureMessagingSDKClient.h is not intended for public use, it is an internal C++ header, not the SDK's umbrella header. If your project imports this header directly, update your import statement as follows:
Change from
#import <MSSSecureMessagingClient/SecureMessagingSDKClient.h>to
#import <MSSSecureMessagingClient/MSSSecureMessagingClient.h>MSSSecureMessagingClient.h is the SDK's umbrella header and should be used for all integrations going forward.
A deprecation notice for
SecureMessagingSDKClient.hwill be added in an upcoming release, and it will be removed from public headers in a future version of the SDK.
General issues
Storage lost on Asus Zenpad 7.0 when device has PIN enabled
On Asus Zenpad devices protected by a PIN, the device could terminate unexpectedly after short usage of the storage (i.e. approximately 30 storage accesses), and the storage would be lost. This issue is due to an incorrect manufacturer implementation, and has been reproduced on an Asus Zenpad 7.0 Z370KL device.