1

Unable to open tasker if it is left on a locked project

I thought I posted this a little while ago but I'm not sure if it was actually posted/visible so I'm trying again.

I do NOT have "lock on startup" enabled.

I have several projects. A few of them are locked with the lock code, whole others (including home) are not.

If I am in one of the locked projects, and then leave or close the app, then when I next open the app, it starts up in that project, not home - which is fine. But because it is a locked project, I am naturally prompted for the lock code. However, if I don't have the lock code, then it forces me to leave the app. Pressing "cancel" exits Tasker, and I am unable to switch to any other projects.

This is problematic because there's no way to do anything in the Tasker app without getting the lock code (or perhaps clearing cache, force stopping, or rebooting). However, I only wanted to lock some projects; not all of Tasker. (I do not have the "lock on startup" option enabled.)

I think it should allow for the option to switch to another project that isn't locked, given that "lock on startup" is not enabled. Or, maybe just allowing the user to choose a default project that Tasker displays when it's opened (as opposed to just the must recent one).

Attached should be a video of the behavior:

https://streamable.com/dbw765

Follow

1 reply

Votes Newest Oldest

Hi. Thanks for the report. Just so I can understand the situation better, why don't you have the code in that situation?

Comment
A

It's a device used by two people and only one of them should have access to these specific projects (but the other person should be able to access other parts of Tasker).

But I now realize that this is a much more niche use case for the lock feature than I initially thought it was, so I understand that it isn't really that important compared to other issues that affect more people.

I understand. I'll leave it open, but I  won't prioritize it for now. Thanks!

Reply