Introduction
Welcome to OneSpan Mobile Authenticator Studio 5.5.0!
For more information about integrating, configuring, and using Mobile Authenticator Studio, see the Integration Guide and the Product Guide.
Supported platform versions
Mobile Authenticator Studio 5.5.0 supports the following platforms:
Android
Minimum: Android 7.0 (API level24) and later
Target: Android 16 (API 36)
iOS
Minimum: iOS 15
Xcode 16
Format of the installation files
For the installation of Mobile Authenticator Studio, OneSpan will provide the installation files in the following formats:
IPA for iOS
APK and AAB for Android
Deprecations
End-of-life (EOL) notice for previous product versions
All versions of Mobile Authenticator Studio 5 prior to version 5.5.0 have reached End of Life (EOL), and support for these will end on 25 November 2027. To ensure continued support, security, and access to the latest features, we strongly recommend that all customers adopt version 5.5.0 as the baseline version for Mobile Authenticator Studio 5 going forward.
For exact dates as well as EOL information for Mobile Authenticator Studio 4, refer to our Product Life Cycle page.
New features and other changes
Support for non-secure channel transactions in multi-device licensing integrations
Mobile Authenticator Studio now also supports transactions in multi-device licensing (MDL) integrations via a non-secure channel. You can now integrate manual request approvals and signatures in both single-device and multi-device licensing integrations. This new feature includes generating one-time passwords and e-signatures to process the following operations:
Approve signature requests manually
Manual transaction data signing
Transaction data signing via Challenge/Response (also supported in integrations with DIGIPASS Gateway)
Approve signature requests by manually scanning a QR code or colored QR code (Cronto image)
For more information, see Request approval methods.
Display end user license agreement
Mobile Authenticator Studio can now be configured to display an end user license agreement (EULA) after the app has been installed. The user must accept the terms. This is a one-time agreement, as soon as the user has accepted the terms, the EULA will not be displayed anymore, even when you update to a new version of Mobile Authenticator Studio. This feature provides multi-lingual support and enables you to display the EULA in the languages you want to use in your project.
For information how to integrate this, see Integrate displaying an end user license agreement.
Post-activation device binding
Mobile Authenticator Studio now supports device binding. Once Mobile Authenticator Studio has been activated locally, the server must receive the information to ensure that both parties are synchronized. Device binding is an enhancement of the regular server activation process and is a Mobile Authenticator Studio post-activation process.
For further information, see the following articles:
Offline Scan and Sign (DPGW)
Mobile Authenticator Studio now supports the offline scan-and-sign workflow via DIGIPASS Gateway.
Migration information updated
Mobile Authenticator Studio supports the migration of all previous versions, from both, series 4.x and 5.x, to the current version, 5.5.0.
Mobile Authenticator versions before 4.30.9 are no longer supported. You are free to validate if migration scenarios are successful, however, we recommend that you update to at least version 4.30.9 before migrating to any 5.x version of Mobile Authenticator Studio.
For more information about migrating and updating, see Migration between versions of Mobile Authenticator Studio.
Customizable notification icon
It is now possible to customize the icon to display for a notification from Mobile Authenticator Studio. You can add the icon as a PNG or SVG file in the customization of your integration. If you do not use the customized icon, the app’s launcher icon will be used.
For more information how to integrate this feature, see Notification icon.
Fixes and other updates
Issue MAS-7135 (Support case INC0015363) Incorrect information for migrating a non-protected user account
Description: In the Integration Guide, the information for migrating a non-protected user account from Mobile Authenticator Studio 4.x to 5.x stated that the account must be protected with a PIN and optionally biometric authentication. This is not correct, as Mobile Authenticator Studio 5.x also supports to not protect an app.
Status: The documentation has been corrected, see also Workflows to migrate from Mobile Authenticator Studio 4.x to 5.x.
Known issues
(Issue MAS-5165) PIN no longer works after update on iOS
Description: When a PIN was set on a device that has a keyboard which includes foreign characters instead of digits, e.g. an Arabic keyboard, the PIN no longer works after updating Mobile Authenticator Studio.
Workaround: Mobile Authenticator Studio must be activated again to create a new PIN.
(Issue MAS-5670) No fallback PIN on iOS
Description: On iOS devices, when the user fails two consecutive attempts to provide the FaceID during authentication, the device prompts the user only to cancel the action and dismisses the activation flow.
Workaround: The user can take the following steps as a workaround of this issue:
Retry the authentication and provide the correct biometric method.
Disable the biometrics from the Settings menu and retry to authenticate with PIN.
If biometric authentication has become locked, the user can authenticate with their fallback PIN.