autolock settings not working properly

[tomlinton]

Lots of reports in Discord of autolock not behaving, maybe related to #2985

[wentokay]

are there any specific issues, or have you been able to reproduce anything you've seen?

I've found these searching for 'autolock' messages (since the last chrome store publish) -

"despite me having autolock set to off, i get locked out of backpack (i.e. needing a PW) everytime i click away" - #2985?
"It autolocks within in 2/3 mins" - #2985?
"autolocking is not working well" - ?

[tomlinton]

Nothing specific, just needs digging into. It might all just be #2985.

[wentokay]

never will ask for a password after opening backpack if the service worker has died, i.e. it hasn't been polled with a keepalive message.

So this will always happen if the user quits the browser application itself and possibly if the user has backpack closed for a certain amount of time, although I haven't been able to reproduce that locally

If that's the case it might be best to remove never as an option altogether.

Other wallets using chrome manifest v2 won't have this problem because it's a special type of long-running background script and not a service worker that's designed to be ephemeral.

[tomlinton]

Other reports:

I'm also using brave (on linux) and constantly have to enter password, regardless of lock settings

it the auto lock timer not fully operational yet? tried diff times and even never and it gets locked after closing regardless of setting

You can reproduce this behaviour with the Update on reload setting in dev tools, but I don't think that is what is happening here. It does seem like something is killing the service worker for some reason.

[wentokay]

chrome alarms might help in some cases but not in this case where the SW appears to be terminating with the popup

[armaniferrante]

Going to change to p3. I'm not sure if there's anything we can do about this given the ephemeral nature of service workers. Please feel free to comment if you disagree.