Error initializing Fingerprint Unlock: Java.Lang.RuntimeException: Exception of type 'Java.Lang.RuntimeException' was thrown.

[luckyrings]

Hi Philipp, everybody,

I have a problem with the quickunlock - there is red icon, tapping on it, it shows crash log from the the fingerprint reader. Fingerprint reader works well in other applications.

OS: Lineageos 16.1 (vendor based software and firmware is from Android Oreo 8.1)

The log is attached:

fingerprint.log

Kind regards
luckyrings

[PhilippC]

I cannot tell from the log which version you are running? Please make sure it's 1.08-r1 (https://play.google.com/apps/testing/keepass2android.keepass2android). If it doesn't work there, please try with Keepassdroid or KeepassDX. "Other applications" is very vague as they might not require encryption but just authentication.

[jkmartindale]

I had a similar issue after swapping out Android 9 ROMs on my phone. Keepass2Android synced my settings from Google Drive, I open the same database, and QuickUnlock showed a red icon with a crash log for setting up the fingerprint reader.

When I opened database settings and disabled and re-enabled fingerprint unlock, it worked just fine again. I think the old fingerprints remained in the database or something and were invalidated because of my switch to a new ROM.

[luckyrings]

Hi @PhilippC - I have tried the new version from the invitation link, the new version just crashed when pressing the red sign mark in the quick unlock screen.
The applications KeepassDX and Keepassdroid work fine with fingerprint.

But as @jkmartindale wrote : I was switching the rom from 8.1 to 9 and using the saved database from my dropbox. After I disabled and enabled the fingerprint unlock in the settings it works now fine.

I am not sure if I shoud close it, or leave it open here, as it might be necessary to mitigate this bug in the software. It could be that more users facing this.

[luckyrings]

@PhilippC : to answer which version I was running before I joined the beta program: 1.07b-r0

[benplumley]

I've just come across this issue. For me, the cause was using the Android feature to move apps from an old phone (Moto G4) to a new one (Moto 5G) - it must have pulled config about the old phone's fingerprint reader along with it which then failed with the new phone's fingerprint reader.

disabled and re-enabled fingerprint unlock

This fixed it for me too. Both phones were using the latest non-beta version in the Play store.

[stebuec]

I had the same problem after changing data toi my new phone. First I could not solve the problem. But then I recognizez I had to desctivate bemetric recognitation in the database (Gerrman Datenbank) not in in the application (Anwendung) part of the settings.

[clangsmith]

I encountered this same issue after moving to a new phone (from Pixel 3a to Pixel 6a) (New phone currently has version 1.09c-r0 of KP2A.) Fortunately, like others stated, disabling biometric unlock and then re-enabling it resolved the issue for me as well.

[Retne]

I too got here for the sames reason.
I wonder it it's worth adding something around that error message to point out this entirely reasonable workaround (or more complicated fix: know something about which device the biometric info was last saved on?)

[slenered]

Disabling and re-enabling the biometrics doesn't work on my device. Can anyone help?