PhilippC
[BUG] "Unlocking the database failed" comes regularly
Checks
- [x] I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
I have a database with a keyfile and a password that I use with biometric unlock and quick unlock. Sometimes - I didn't find out the conditions yet - when I have to unlock my database I get the error "Unlocking the database failed: Invaild composite key. Biometric Unlock was disabled ...". When this happens "Select master key type" is reset to Password only and the keyfile, that I imported to the internal folder is gone. This only happens since the last update.
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
1.15-pre0
Which version of Android are you on?
15
Hmm, I am using 1.15-pre0 myself and haven't seen any such behavior. Are you really sure it's not just that you mistyped your password? (I don't want to insinuate that, but I have seen this too often already :-) )
If it continues to happen, can you downgrade to 1.14 and see if it's gone again?
It is a valid question but yes I am sure. I don't type in my passwort but I use biometric unlock. This is basically the same bug: https://github.com/PhilippC/keepass2android/issues/3068 so I'm not the only one. The issue is not the wrong password but the setting resets to password only. I can do the downgrade on the weekend.
Hmm, I am using 1.15-pre0 myself and haven't seen any such behavior. Are you really sure it's not just that you mistyped your password? (I don't want to insinuate that, but I have seen this too often already :-) )
If it continues to happen, can you downgrade to 1.14 and see if it's gone again?
Since I upgraded to 1.15-pre0, I've had the same problem, twice in half a month. And it didn't happen after I downgraded.
Details: The database is unlocked with "password + key", and the key file is imported to an internal folder, with biometric fingerprint recognition and quick unlock enabled. After a few days of use, the key was lost when I encountered a failed quick unlock, and the database unlock mode was changed to "password only".
@sahriVoraus did this happen for you also after quick unlock (with or without fingerprint?) or was it after a "full unlock" attempt?
@Bedingled403 are you sure that this happened after quick unlock? Because the error reported in the OP "Unlocking the database failed: Invaild composite key. Biometric Unlock was disabled ...". means that there it happened when doing a full unlock.
@Bedingled403 are you sure that this happened after quick unlock? Because the error reported in the OP "Unlocking the database failed: Invaild composite key. Biometric Unlock was disabled ...". means that there it happened when doing a full unlock.
Sorry, as I encountered this error a few days ago, I may not be able to provide further specific details. I will provide feedback in time to provide more thorough details the next time the issue arises.
What I can say for sure, though, is that after turning on quick unlock and fingerprint unlock, I stopped using full unlock until the unlock failed and the database mode automatically changed to "password only", and the keyfile in the internal folder was lost. And I use HTTPS(WebDav) to connect to my database.
BTW, I guess the crux of the matter may be that no matter what kind of unlocking fails, it shouldn't result in the loss of the keyfile in the internal folder. After all, if the keyfile had not been lost, a simple reset would have been required to continue using it. But now it would have caused the password database to fail to synchronize.
@sahriVoraus did this happen for you also after quick unlock (with or without fingerprint?) or was it after a "full unlock" attempt?
it always was on a full unlock. Normally I use Quick Unlock but every now and then (maybe app was closed in the background) a full unlock is necessary. The issue doesn't happen on every full unlock though. I didn't find the pattern yet.