Introduction
Welcome to OneSpan Mobile Authenticator Studio 5.6.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.6.0 supports the following platforms:
Android
Minimum: Android 7.0 (API level24) and later
Target: Android 16 (API 36)
iOS
Minimum: iOS 16
Current version: Xcode 26
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.6.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
iOS minimum supported version increased to 16
As of this version, the minimum version of iOS supported by Mobile Authenticator Studio is iOS 16.
Support for Xcode 26
As of this version the Mobile Authenticator Studio app is built in Xcode 26.
Auto-launching the app for activation
Mobile Authenticator Studio 5.6.0 supports the automatic launch of the Mobile Authenticator Studio app for activation flows. With this feature, the app can be invoked from a URL that has the following format:
${scheme}://${actionName}
This URL can be provided to the user in a mobile web browser or called from a third-party application. For more details and information how to integrate this feature, see Integrate auto-launching the app.
New DIGIPASS Gateway workflows
With this version, additional DIGIPASS Gateway workflows are supported. Accordingly, the following Mobile Authenticator Studio features are new or have been extended:
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.