Closed loeffelpan closed 2 years ago
Which version?
That happened over longer period. Shoud matter more than one version.
Latest was with 1.29.100.
Edit: I had another device with 1.27 and just made an update. Before the update TouchID and master key unlocked the DB. After updating to 1.29.100 it asks for password and keyfile.
I have asked about the version because there was a relevant fix 1.30.101 (beta):
AutoFill could lock up the database when running low on memory [thanks, Tim]
In general, these are the reasons why KeePassium can have the database locked:
The latter happened in 1.28, where stored keys were additionally encrypted by Secure Enclave. The new version was supposed to automatically convert stored master keys into new format, but due to a bug it failed to read the old data. I got this fixed in 1.30.101, and paused automatic rollout of 1.29.100 (the latest App Store version) until the fixed version is beta-tested and ready for the App Store.
Thanks. So maybe lastest times this happened was due to that bug after updating to 1.29.100 with key conversion.
I‘ll have an eye on it next time that happens and (hopefully not) open another issue.
Happy new year and stay healthy.
I‘m wondering why KeePassium sometimes asks for the db password. Nothing changed. Masterkey should be valid. Face/Touch-ID for the App Passcode was successful. Timeout is set to „Never“.
Most times that work. Sometimes/Suddenly not.
Can you please list the cases KeePassium will ask for db password? Maybe I‘m able to figure it out.