Lock timeout not really respected
Hello,
This is what I've set:
Lock 1Password after browser is idle for = 300
Unfortunately, very often I notice the extension is locked while Chrome hadn't been idle for 300 minutes. It gets locked way sooner and way too often. Anyone sees the same?
Thanks,
Dominik
1Password Version: Not Provided
Extension Version: 0.8.6
OS Version: Ubuntu 17.04
Sync Type: Not Provided
Comments
-
@Dominik_Skorka: We've found what we believe is a bug in the chrome.idle API we are using to check if your computer has entered an idle state. I'm in the process of testing a fix for this, which pending any issue will be included in a build in the near future.
--
Andrew Beyer (Ann Arbor, MI)
Lifeline @ AgileBits0 -
Thanks @beyer . I guess that the fix didn't hit 0.9.0, did it?
0 -
@Dominik_Skorka: 0.9.0 should be working well when it comes to auto-locking. Please note that if your device locks or goes to sleep 1Password will lock (no matter the time that has passed). However, if you're actively logged in and using your device, 1Password shouldn't be locking until after the time you have set on the settings page.
I'd be very interested if you're seeing something different on your end. Please let me know.
--
Andrew Beyer (Ann Arbor, MI)
Lifeline @ AgileBits0