randomly locking before the time of the autolock, likely everytime that there is a refresh of the client

[Fabricio333]

[leonacostaok]

ok found it. two things going on here.

the autolock interval only lives in memory in the service worker, and chrome kills the service worker all the time (incl. on page refreshes). when it comes back it resets to the default 15min instead of whatever you had configured. and worse — the unlocked vault key is in memory too, so a refresh that restarts the worker basically makes it look locked even tho your timer hadnt elapsed. thats why it felt random / every refresh.

fixed in v0.3.84:

• restore the configured autolock interval from storage on unlock + on startup instead of falling back to 15min
• added a keepalive (chrome alarms) that keeps the worker alive while the vault is unlocked so the real timer actually governs the lock. we dont persist the key, just keep the worker warm

should stop the early locks. lmk if you still see it after updating