- 23 Oct 2024
- 1 Minute to read
- DarkLight
- PDF
Version 4.30.0 (January 2023)
- Updated on 23 Oct 2024
- 1 Minute to read
- DarkLight
- PDF
Fixes and other updates
Android
[LMAS-1785][CS0103957] Wrong input filter for the pin fallback dialog
When a PIN was entered as a biometric authentication fallback, the maximum password length configured in the static vector was not enforced. The hardcoded ACTIVATION_PASSWORD_MAX_LENGTH was used instead.
This issue has been fixed.
[LMAS-1829] [CS0111665] Push Notification permission text not customizable on Android
Mobile Authenticator Studio 4.28.7 introduced a new permission called NotificationsUsageDescription and it includes a message to display when notification permission is needed. However, the default text was not editable. In this release, the text can be changed in the XML customization file. For more information on how to customize the text, see the OneSpan Mobile Authenticator Studio Customization Guide.
This issue has been fixed.
iOS
[LMAS-1812] [INC0011516] Application crash with specific push notification setup
In Mobile Authenticator Studio 4.28.7, an application crash occurred in a configuration setup with a server that sent notifications containing custom attributes. Mobile Authenticator Studio has been updated to accept integers in addition to strings in the custom attributes of the received payload.
This issue has been fixed.
[LMAS-1814] [INC0011534] Missing bundle name in info.plist file
In a previous release, some customers may have seen the warning ITMS-90784: Missing bundle name when trying to publish Mobile Authenticator Studio applications to the iOS App Store. The missing Bundle name and Bundle display name have been added to the info.plist file.
This issue has been fixed.
[LMAS-1837] [INC0011709] Missing purpose string and description in info.plist file
In a previous release, some customers may have seen the warning ITMS-90683: Missing purpose string in Info.plist when trying to publish Mobile Authenticator Studio applications to the iOS App Store. This was due to a missing property in the info.plist file. The property NSLocationAlwaysAndWhenInUseUsageDescription, along with a purpose description, have been added to the info.plist file.
This issue has been fixed.