Release Notes Mobile Authenticator Studio—Version 5.4.0 (August 2025)

Prev Next

Introduction

Welcome to OneSpan Mobile Authenticator Studio 5.4.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.4.0 supports the following platforms:

Android

  • Minimum: Android 7.0 (API level24) and later

  • Target: Android 16 (API 36)

iOS

  • Minimum: iOS 15

  • Swift 5

  • Xcode 16 and later

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

New features and other changes

Compliance with European Accessibility Act (EAA)

Mobile Authenticator Studio has been updated to comply with the minimum requirements as foreseen by the European Accessibility Act (EAA) and Level A and AA Conformance of the Web Content Accessibility Guidelines (WCAG) by the World Wide Web Consortium (W3C). The following features have been introduced and/or updated to ensure meeting the minimum accessibility requirements:

  • Screen orientation: landscape mode is now also supported.

    The device can be used in any orientation and the Mobile Authenticator Studio app flows and features work as designed in either mode.

  • Screen readers (TalkBack on Android and VoiceOver on iOS)

    Icons, app control elements, and actions are read aloud, and the user can navigate and control the Mobile Authenticator Studio app with swipe and finger-tap actions.

  • Text resizing: text can now be maximally resized without loss of information or functionality and without requiring the user scrolling in two dimensions.

  • External keyboard support: the user is now able to do most actions via keyboard and has adequate time to complete tasks.

  • Adjustable timing: Mobile Authenticator Studio now informs the user about the time a generated one-time password remains valid.

For more detailed information, see Accessibility in Mobile Authenticator Studio. By integrating this version of Mobile Authenticator Studio, your app complies with minimum requirements foreseen by the EAA and WCAG.

PIN management screens: new design

The design of the Mobile Authenticator Studio PIN management screens has been updated to ensure minimum compliance with the European Accessibility Act and Web Content Accessibility Guidelines for input assistance. The screens have been updated with the following changes:

  • PIN input field: Mobile Authenticator Studio now uses the fully native secured component on Android and iOS.

  • A Done button is added in every PIN management screen

  • Copy/Paste: the app allows the keyboard Copy/Paste feature to avoid transcription and copying content from an outside source (e.g. a notes app on the device) and paste it in the PIN field in the Mobile Authenticator Studio app.

  • Avoid hiding characters/allow unhiding of characters: apps should not hide characters while typing.

These changes affect all PIN management screens, including the following workflows:

  • Enter PIN (Authentication)

  • Choose PIN (during activation)

  • Confirm PIN (during activation)

  • Change PIN (from the Settings menu)

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:

  1. Retry the authentication and provide the correct biometric method.

  2. Disable the biometrics from the Settings menu and retry to authenticate with PIN.

  3. If biometric authentication has become locked, the user can authenticate with their fallback PIN.