search

aivanovski / keepassvault

KeePass client app for Android
Apache License 2.0
42 stars 2 forks source link

app crash on db ulock #249

Closed makinghappen closed 4 weeks ago

makinghappen commented 1 month ago

Overview

App crashes instantly when trying to unlock db, both with password and biometrics. Haven't been using it for a while, probably it has got updated automatically to 1.4.1. Log is not being collected and is empty.

How to reproduce

  1. Open the App
  2. Try to unlock
  3. App crashes

Version

1.4.1

Android Version

13

Device Model

Samsung S24

makinghappen commented 1 month ago

I also cannot reset app data to check, because I don't remember the password and would rely on biometric unlock

aivanovski commented 1 month ago

Hi, Without the stacktrace it cannot be fixed. Could you connect your device to PC and collect it? It could be done in Android Studio or in terminal https://developer.android.com/tools/logcat#Syntax @makinghappen

blkhawk commented 1 month ago

This sounds suspiciously like what I was about to open an issue for. I have a better Idea what could have caused it since I did something before it started crashing. I re-registered one of my fingers because the failure rate was too high. This obviously invalided the key for the biometrics. Other apps prompted for a password after that - KPV however just crashes if you try to use the fingerprint afterwards. Disabling the biometrics in the settings work however re-enabeling the biometrics afterwards seems to reuse the old key and causes an exception / crash.

I attached a log-file with the crash in the settings dialog. I think that maybe catching the exception ,then purging the key from the configuration might help?

A Workaround is probably to completely reset the app and redo the configuration.

Version 1.4.0 (f-droid) on GrapheneOS (Pixel 7a)

Log-file KeePassVault log 7bef9a6a1e62.txt

makinghappen commented 3 weeks ago

@aivanovski thank you for fixing, could you release a new version to f-droid? it seems that the version released on Github has a different signing key and I cannot update

aivanovski commented 3 weeks ago

@makinghappen F-droid uses its own signing key, it's part of the f-droid policy. And unfortunately the f-droid release process is very slow, usually f-droid automatically detects new releases at some point and then builds and releases new version. This process can take several days or even week. I don't know if there is any way to speed it up. Yesterday I published update into Google Play, it should be available soon, tomorrow I hope.