BUG? MLO-Android: "Lock profile" requires passcode no matter the time set in "Require Passcode"

68 views
Skip to first unread message

Roberto Penzo

unread,
Dec 27, 2017, 7:22:27 AM12/27/17
to MyLifeOrganized
Hi all.
I am running MLO Android rel. 2.12.0.

Long time ago, on the "Lock Profile" setting I set a Simple Passcode on "Lock Profile", and I also set a 2 hours time on the "Require Passcode" option.
It worked fine until a certain date (a certain release? which one?), but now, on 2.12.0, it requires me to enter the passcode every time I launch MLO, no matter how much time has passed from the last time I launched it.

Someone of you is experiencing the same as me?

Thank you very much.

Roberto from a city near Venice, Italy.

Roberto Penzo

unread,
Jan 11, 2018, 4:40:50 PM1/11/18
to MyLifeOrganized
Update: if I choose "15 seconds" as the timeout, it works well. With other timeouts it does not work.

Alyona (MLO Support)

unread,
Jan 12, 2018, 9:34:32 AM1/12/18
to MyLifeOrganized
Hi Roberto,

If the app is unloaded from the memory, you need to enter the password again.

Andrei Bacean

unread,
Jan 13, 2018, 10:58:13 AM1/13/18
to MyLifeOrganized
Hi Alyona
I also see this ?bug.

To reproduce:
Set the interval to 2h.
Create an mlo widget (widget which displays tasks) on android screen.
Run mlo from the standard mlo shortcut.
Enter password.
Press home to switch to the android Homescreen.
Run mlo from the WIDGET!!
The password screen will be displayed again. (Instead if you run mlo from its default shortcut, the password screen won't be displayed).
So it seems to be a bug.
BR
Andrei

Alyona (MLO Support)

unread,
Jan 15, 2018, 10:03:40 AM1/15/18
to MyLifeOrganized
Just checked with the developers that it's not a bug. The main principle there: it's better to ask a password once again than miss it. Through the widget you can enter not only the current but any profile. Therefore, the countdown is carried out separately there. But the next time you use widget, it shouldn't ask a password earlier than in 2 hours.

The developers are going to reconsider the existing algorithm.
Reply all
Reply to author
Forward
0 new messages