keepass2android icon indicating copy to clipboard operation
keepass2android copied to clipboard

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

Open luckyrings opened this issue 5 years ago • 10 comments

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

luckyrings avatar Feb 21 '20 10:02 luckyrings

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.

PhilippC avatar Feb 23 '20 06:02 PhilippC

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.

jkmartindale avatar Feb 24 '20 18:02 jkmartindale

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 avatar Feb 24 '20 21:02 luckyrings

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

luckyrings avatar Feb 24 '20 21:02 luckyrings

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.

benplumley avatar Aug 14 '20 10:08 benplumley

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.

stebuec avatar Mar 22 '22 10:03 stebuec

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.

clangsmith avatar Jan 06 '23 04:01 clangsmith

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?)

Retne avatar Jul 21 '23 17:07 Retne

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

slenered avatar Aug 30 '24 21:08 slenered

Same here, I tried disabling the biometric unlock, as well as reinstalling the app, but nothing works, the Java.Lang.RuntimeException persists.

ykneisel avatar Feb 27 '25 11:02 ykneisel