--- title: "Release Notes Mobile Authenticator Studio—Version 5.7.0 (June 2026)" slug: "mas-release-notes-5-7-0" updated: 2026-06-23T07:13:54Z published: 2026-06-23T07:13:54Z canonical: "docs.onespan.com/mas-release-notes-5-7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Release Notes Mobile Authenticator Studio—Version 5.7.0 (June 2026) ## Introduction Welcome to OneSpan Mobile Authenticator Studio 5.7.0! For more information about integrating, configuring, and using Mobile Authenticator Studio, see the [Integration Guide](/mobile/docs/mas-5-integration-guide-5-7-0) and the [Product Guide](/mobile/docs/mas-5-product-guide-5-7-0). ## Supported platform versions Mobile Authenticator Studio 5.7.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.7.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](https://www.onespan.com/support/security/product-life-cycle#mobile) page. ## New features and other changes ### Auto-launching enhanced The feature to auto-launch the app has been enhanced and now also supports integrating the automatic App2App launch of multiple authenticator actions, such as One-Time Password, Challenge/Response etc. This allows secure and frictionless authentication and signing workflows across applications. The function range corresponds to the same feature available in Mobile Authenticator Studio 4.x. ### Documentation improved: tablet compatibility The Product Guide has been improved. Information about the compatibility of the Mobile Authenticator Studio app for tablet usage has been added. For more information, see [Device compatibility](/mobile/docs/mas-5-pg-device-compatibility-5-7-0). ## Fixes and other updates Issue MAS-7861 (Support case INC0016168) Migration issue: failed post-activation in multi-device licensing mode **Description**: During the migration from Mobile Authenticator Studio 4.x to 5.x, a post-activation step failed. In multi-device licensing (MDL) mode, the process failed after Activation Message 2 was scanned, causing the 5.x-based app to return an error. **Status**: This issue has been fixed. For more information about migration, see also [Workflows to migrate from Mobile Authenticator Studio 4.x to 5.x](/mobile/docs/mas-5-ig-workflows-to-migrate-from-4x-to-5x-5-7-0). Issue MAS-8078 (Support case INC0016501) App-to-app signature not redirected **Description**: On iOS, an issue in the app-to-app signature flow prevented the return signature from being redirected to the correct callback URL and browser, causing the process to fail. **Status**: This issue has been fixed. Issue MAS-8112 (Support case INC0016546) Compatibility issues with OneSpan Cloud Authentication **Description**: Mobile Authenticator Studio 5.x was not compatible with OneSpan Cloud Authentication, due to an issue with different URL resolution methods. **Status**: This issue has been fixed. ## 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.