Open alex-siqueira opened 7 years ago
Hi Alex,
Is it possible to provide details about your device, e.g. the model, OS level, and the app that you're using? I cannot reproduce this issue on a 4.4 and a 7.0 emulator and pressing the back/cancel button just takes me back to the app.
By default, the lockscreen must be enabled for the MAS security features to function, as we are using credential storage; the pop-up that you see is launched by the OS when trying to access these credentials (see AccountManager for further reading). However, you can implement Token Storage as described here as an alternative to using the lock screen.
Hi everyone:
I've managed to reproduce this issue in two Motorola devices (Moto G and Moto G5) running Android KitKat. I've also tried to reproduce this behavior in my Nexus 5X phone (Android Oreo) but, on this device, the application worked properly.
I still haven't got the chance to test the 1.5.00 version. This is the next step...
Greetings!
I believe I found an issue that affects Android apps using MAS SDK: the first time you launch an App and the device has no Lock Screen method selected (neither PIN, nor Pattern, nor Fingerprint...), SDK fires the Settings Page asking for Lock Screen method selection. If the user hits "Cancel" or "Back" on this screen, the device gets stuck and the app freeze.
That issue rise some questions:
Is it mandatory that Android devices have Lock Screen enabled to use MAS SDK Apps?
Can we disable this behavior (for MASFoundation use only)?
Is it possible to fix this issue, either showing a message saying "Lock Screen is mandatory" or adjusting the SDK?