Version 4.28.5 (May 2022)

Fixes and other updates

Android

[CS0080804][LMAS-1444]: There was an issue in which the Replace Instance feature did not perform as expected when the activation information was manually entered on both iOS and Android.

This issue has been fixed.

[CS0091246] [LMAS-1728]: There was an issue with Mobile Authenticator Studio-Enterprise Security on certain Samsung Galaxy devices in which an app would fail to start and the user would see a black screen.

This issue has been fixed.

[LMAS-1743]: The .apk file in the Mobile Authenticator Studio Enterprise Security product package has been renamed from DPMOBESA.apk to OneSpan MA_ES_<version number>.apk.

[LMAS-1752]: The Android target API has been updated to Android 12 (i.e. API level 31), to meet the new submission guidelines for Google Play Store coming in November 2022.

[CS0086545] [LMAS-1710]:Google Play Permissions Declaration If your app relies on the use of sensitive permissions, you are required to complete the Permissions Declaration Form to make your app available in Google Play.

The Permissions Declaration Form is displayed during the release process if the app includes an app bundle that requests permissions for which a Permissions Declaration has not been provided to Google Play.

If you have an active app bundle that requires a Permissions Declaration, including releases on the Open, Closed, or Internal test tracks, an alert is displayed on the left menu under App Content. You cannot publish any changes to your app, including changes to your Store Presence (for example, Store Listing, Pricing, and Distribution) until you address this alert. You can either create a release that includes a Permissions Declaration or remove the permissions from that app.

To complete the declaration in the Google Play Console, go to App Content > Start Sensitive app permissions >  Location Permission page or App Content > Permission Declaration form.

If the app does not contain features that use sensitive permissions, the Sensitive app permissions flag will not show up on the App Content section.

Additionally, consider deactivating any Open, Closed, or Internal testing tracks that are not currently in use if they are not compliant with this policy. If you publish apps using the Google Play Developer Publishing API, consult these special instructions.

You can also visit the Play Console Help page for the steps to complete the Permissions Declaration Form. The following figure shows an example of the App Content page on the Google Play Console.

Google Play Console App Content page

If your app does not contain or need any permissions declaration, Sensitive app permissions will not show up on the App Content section of your app’s Play Console page and you do not need to complete the declaration form.

iOS

With the next version of Mobile Authenticator Studio, the minimum supported iOS version will be iOS 13.

[CS0080804][LMAS-1444]: There was an issue in which the Replace Instance feature did not perform as expected when the activation information was manually entered on both iOS and Android.

This issue has been fixed.

[CS0086232] [LMAS-1745]: A security vulnerability was fixed by improving the tools used to compute the cryptographic random operations.

[CS0089186] [LMAS-1718]: There was an issue with the installation and activation of a new application using Mobile Authenticator Studio on devices running iOS version 15. The problem occurred if that device never had an application with Mobile Authenticator Studio previously installed on it.

This issue has been fixed.

[CS0092115] [LMAS-1749] Thread managements has been modified to fix a crash in some specific Biometric authentication flows.