Hi folks,
I would highly recommend using Sync as this should eliminate this problem from happening. This is likely what a lot of Chrome users are doing - signing in with their Google account. Same w/ Edge users and signing in with their Microsoft account.
This problem does actively happen with Chrome too - and the exact steps are very important. We’ve proactively spent a lot of cycles debugging suspect areas of the code. It’s definitely not an easy problem to solve.
There are some things we can do - like log to a system log when the password used for encrypting/decrypting passwords changes. That might help us tie a date/time to an event the user did on the OS which we haven’t found a root cause for yet. For example, if we had that timestamp, we could check event viewer on Windows or syslogd on Linux and see what else happened around that time