Known issues

Known issue in Mobile Authenticator Studio

This chapter lists issues that have not yet been resolved for the current Mobile Authenticator Studio version. In addition, this chapter provides information about possible workarounds, if available.

Device fingerprint per app from Android 8.0 (Oreo)

For Android 8 (Oreo) and later, the Device Identifier is now unique per app instance, instead of per mobile device. Each app has a specific Device Identifier and this Device Identifier does not change if the app is reinstalled.

In case of migration to Android 8.0 (Oreo), backward-compatibility is ensured by the operating system, which keeps the old Device Identifier until the app is uninstalled. The migration to Android 8.0 (Oreo) will not cause any issues (e.g. storage lost, validation failure). After migration and re-installation of the app, the Device Identifier changes and becomes unique for the app.

DIGIPASS for Mobile – iPhone edition and Biometry feature

On iOS 14 and earlier, the Biometry feature on a DIGIPASS for Mobile application will not work if a second DIGIPASS for Mobile application with the same version is deployed on the phone and is actively using the Biometry feature. In this case, the Biometry feature will always return an error. This operating system error has been corrected with iOS 15.

DIGIPASS for Mobile – iPhone edition binary deployment

The DIGIPASS for Mobile – iPhone edition binary cannot be deployed on iPhone devices with iTunes 10.3.1.55 running on a Windows 7 operating system if it has been configured with a EULA including non-Latin characters.

DIGIPASS for Mobile 3.X – iPhone edition update

The update of a DIGIPASS for Mobile 3.X by a DIGIPASS for Mobile 4.X forces the user to reactivate due to a change in the device fingerprint provided by the platform.

Activation interruption with power button

On iOS, if the user interrupts the activation flow by pressing the power button between the activation and post-activation processes, the application is not restarted when the user powers on the device.

Network connection through proxy

DIGIPASS for Mobile does not support network communication through proxy. This will fail on most mobile devices.

Activation lost on Asus Zenpad 7.0 when device has PIN enabled

On Asus Zenpad devices protected by a PIN, the device could crash after short usage of the app (e.g. activation and generation of a few OTPs), and the activation would be lost. This issue is due to an incorrect manufacturer implementation, and has been reproduced on an Asus Zenpad 7.0 Z370KL device.

Customization Tool window not completely displayed on low resolution screen

The size of the Customization Tool window is 1000 by 630 pixels. If the display screen resolution is lower than that, the Customization Tool is not displayed completely.