[FEAT] Bug password+biometric

[Nanouy]

If I only enter the password I have no problems, but if I enable biometric authentication, it opens the first time, and then after syncing the file to the cloud (Dropbox, Google Drive, or another service), when I try to open it again...It displays a pop-up warning that the key set is invalid, forcing me to import or restore a backup to use it without problems. That is, unless I activate biometrics.

[PhilippC]

can you please add more details (Android version, app version...) and maybe even a screencast?

[GitNoob-5782]

Hello! I had to make a new account, since I also lost access to my old GitHub account and stumbled on Nanouys Bug report. I think I came across the same bug as them.
I have had a similar issue, where I used the Keepass2Android with Biometric Authentification for Quick unlock, but always opened up the database with the real password. Since having an issue with the reliability of the biometrical sensor, I decided today to remove the Biometrical Authentification because I anticipate that the sensor will fail me sooner rather than later. After deactivating the setting for the Bio Authentification, I logged into the database normaly, but after successfully logging in and closing it, I later ran into the similar described issue of Nanouy - with the weird exception, that my password that I never changed suddenly was throwing the exception

"[Path to .kdbx file]
Failed to load the specified file!
The master key is invalid!
Make sure the master key is correct and try again."

The only issue is - I never used the key feature and never had to change my password. The only change I made since using the Keepass solution for storing passwords was the afformentioned deactivation of the Biometrical Authentification.

Using backups ended up corrupting said backups as well and now I have one backup file left, that I am unwilling to touch and that I now replicated like a madman. Trying Keepass on Windows to maybe restore the kdbx database resulted in multiple errors as well.

I could not replicate it at the moment with a new database that I used for testing (Creating a new database, filling it with dumb values, activating Biometrics, sporadingly opening and closing it for an hour, then removing Biometrics), but I feel like this is more of a version spanning problem.

I installed Keepass2Android around April last year and used it.
I hope this helps somewhat in narrowing down the problem.

[Nanouy]

Hi, the problem persist.
The fail appears when activated biometric opcion, run once and then launch pop-up where inform database corrupt.-
In my case, the error appears with existent database and new database.
Android 14, Xiaomi note 10, Samsung S22, Samsung S10, Samsung Note and other dispositives with biometric sensor

[PhilippC]

none of you has reported the app version you are using. please do so.
@Nanouy are you saying you can reproduce this reliably? If so, can you please record a screencast (disable screen protection in the app settings)s?

[GitNoob-5782]

Oh my bad, sorry.

Version 1.14-r4 is the version, in which the bug occured for me.

[Nanouy]