New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash, inaccessible kdbx and recovery method #362
Comments
Sorry, confused the build numbers.. the only crashes I can see in the play store console are from 1.9.11+2002 |
Happy to help, its for this reason, I have not yet refreshed/reinstalled the app. The LG oreo is a stock rom/production build. so maybe less logs than a developer build.
Does it reveal anything? hth |
Today 20240228, by habit, I opened authpass on my phone and I was surprised that it worked. At this point,
It is strange that the version number still remains the same 1.9.11 Still there needs to be a easy way for the user to recover from the issue. the kdbx should not be trapped and inaccessible inside the android app data folder. I was scared to uninstall, reinstall app, because I did not want to lose anything. I leave it to your judgement as to whether to close this issue. |
Describe the bug
I had a troublesome old battery that would occasionally switch-off-phone due to low capacity.
Perhaps one such abrupt phone-switch-off, may have rendered the authpass app in an unstartable state
On starting the app, android would complain
Unfortunately, authpass has stopped
and askopen app again?
.More panic inducing, was that, there was no easy way to get the kdbx file from the phone.
I thought I lost all my recent passwords. (though I have a backup older by a few months)
I have since got a new battery.
I had tried many methods to recover the kdbx.
I have documented below a method using
adb backup
that allowed me recover the kdbx fileTo Reproduce
While in the crashing state, the app will always behave so whenever started, even after a phone reboot.
If I were to refresh the app installation, by erasing its data+cache, which I will do in a few days, I expect that the new-like app will certainly not have this starting problem. But, I don't think there is a direct way for the user to put the app back into this crashing state.
Expected behavior
I don't think the app is crashing because the kdbx is corrupt/invalid. Some other file/data that it needs before opening the kdbx might be the problem. Quite possibly the blame might be on the QuickUnlock. It crashes even before authpass gets to ask and confirm the fingerprint.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
One cannot browse
/data/user/0
no user permission to descend into this partition./storage/emulated/0/Android/design.codeux.authpass
does not have any files in the subfoldersfiles
orcache
Other things I had tried
/dev/block/dm-1
also can't be adb pulled due to lack of user permissionThe recovery method that saved me
Then, as a user, I run Authpass on linux, create an empty database and close Authpass,
Then, I overwrite the newly created kdbx.
Authpass on Linux, on next start, prompts for password and opens the kdbx. The passwords are intact.
The text was updated successfully, but these errors were encountered: