You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KeePassDX forces close the database after entering password and keyfile.
I have recorded it in an emulator, same result as in my phone. I cleared the encryption key for biometric same result. KeePassDX force close my KDBX 4 database after I entered the password and keyfile.
To Reproduce
Steps to reproduce the behavior:
Input Password and select keyfile in the database credential unlock tab.
Click on 'Device unlock link' or just unlock it without biometric.
KeePassDX does open it for a split second, and then force close the database (weirdly not force closing the app itself).
See error (database force closed, can't open or enter it).
Expected behavior
Database is opened and I'm presented with the root of my KDBX vault directory.
KeePass Database
Created with: Windows KeePassXC 2.7.9 (by changing the category name from Bitwarden, I made it by importing BW .CSV into KDBX 4 format, using a guide from reddit).
Version: KeePassXC version 2.7.9, KDBX version 4]
Location: Local but uses Syncthing to sync it with KeePassXC (using TroubleChute guide to KeePass). (a.k.a., local but shared using P2P sharing app)
File provider (content:// URI): content://com.google.android.apps.docs.storage/5 fourth edit, I'll also post the URL from X-Plore like other user have done:
content://com.lcg.Xplore.FileContent/uid/file%3A%2F%2F%2Fstorage%2Femulated%2F0%2FKeePassMainMobile%2FPasswords.kdbx?size=1436377&time=1732978156240
(IDK, what that is. The storage syncing app version? I use syncthing-Fork so com.github.catfriend1.syncthingandroid.debug version 1.28.0.0)
Alright, after reading the wiki link by pressing top left info button, I think this is the file picker being used, right? I can't change mine so it always uses default documentsUI by Google.
Size: my main vault is 1.4 MB. I have 5 vaults tho. but let's focus on the main one. most of my passwords are in that one
Contains attachment: Yes (2FA recovery codes encrypted and compressed in deflate).
KeePassDX:
Version: 4.1.1 (same result in my old one in shelter work profile: 4.1.0)
KeePassDX version doesn't seem to matter, both 4.1.1 and 4.1.0 can't opened my database. it has been working fine since the first time I know this software from TroubleChute guide video. These past few days, this bug just had happened and is still happening, I think, this doesn't have to do with the app version changing. the internal code maybe to open my database?
Context for my database, I also can't opened it in my KeePassXC but after searching in the internet, turns out for PC, the solution is to install the latest Microsoft C++ redistributable. now I don't think that's possible for mobile.
So what could be the problem, it's fine now in my KeePassXC, the app (KeePassDX) doesn't crash, but crash or force close the database, so maybe a bug in the app database opening mechanism? not sure;
Also how to get logcat, debug or even verbose trace log for this app?
Also the reason, I use an emulator is because I don't have a screen recorder installed, and setting it up is a hassle, so I instead do it on emulator with obs screen capture, and somehow the result is the same. weird, either this is a bug or my database is weird, or my database make KeePassDX process it as an error, not sure. Please debug it if you can.
Warning: some users have noticed corruptions when Syncthing was synchronized at the same time as a data save because the URI stream is cuts by the sync. Please make sure that the two actions are not done at the same time, you can disable the automatic save and remember to make regular manual backups.
Does this have anything to do with my bug, or is it unrelated?
Edit: About the above statement, how do I disable 'automatic save'?
Is it the 'Autosave database' option in KeePassDX's general App settings?
Edit 3:
I get it now the content://URI should be the one below the KDBX database picker drop-down menu tab, right?
Mine is this:
content://com.android.externalstorage.documents/document/primary:KeePassMainMobile/Passwords.kdbx
Also, I didn't screen capture the moment but, when I try to record the logcat in my phone, the first time I try to do it. The app somehow opened my database file, but alas, it's a temporary luck or chance. It's in the bug-mode again, force closing my database.
I hope all of these are enough, if not feel free to ping/@ me, and I'll give you more needed info or logs.
The text was updated successfully, but these errors were encountered:
Describe the bug
KeePassDX forces close the database after entering password and keyfile.
I have recorded it in an emulator, same result as in my phone. I cleared the encryption key for biometric same result. KeePassDX force close my KDBX 4 database after I entered the password and keyfile.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Database is opened and I'm presented with the root of my KDBX vault directory.
KeePass Database
content://
URI):content://com.google.android.apps.docs.storage/5
fourth edit, I'll also post the URL from X-Plore like other user have done:content://com.lcg.Xplore.FileContent/uid/file%3A%2F%2F%2Fstorage%2Femulated%2F0%2FKeePassMainMobile%2FPasswords.kdbx?size=1436377&time=1732978156240
(this one?:content://com.android.externalstorage.documents/document/primary:KeePassMainMobile/Passwords.kdbx)
(IDK, what that is. The storage syncing app version? I use syncthing-Fork so com.github.catfriend1.syncthingandroid.debug version 1.28.0.0)
Alright, after reading the wiki link by pressing top left info button, I think this is the file picker being used, right? I can't change mine so it always uses default documentsUI by Google.
KeePassDX:
Android:
Additional context
similar to: #1848 but probably a different case.
KeePassDX version doesn't seem to matter, both 4.1.1 and 4.1.0 can't opened my database. it has been working fine since the first time I know this software from TroubleChute guide video. These past few days, this bug just had happened and is still happening, I think, this doesn't have to do with the app version changing. the internal code maybe to open my database?
Context for my database, I also can't opened it in my KeePassXC but after searching in the internet, turns out for PC, the solution is to install the latest Microsoft C++ redistributable. now I don't think that's possible for mobile.
So what could be the problem, it's fine now in my KeePassXC, the app (KeePassDX) doesn't crash, but crash or force close the database, so maybe a bug in the app database opening mechanism? not sure;
Also how to get logcat, debug or even verbose trace log for this app?
Attached screen recorded video of the bug:
https://github.com/user-attachments/assets/d23d23c0-fcde-410a-848f-c405db4d2255
As you can see, GitHub renders my video as an error, IDK why, VLC and YT do it just fine. sorry but I'll have to give the video as a YT link: screen recording of the bug
Also the reason, I use an emulator is because I don't have a screen recorder installed, and setting it up is a hassle, so I instead do it on emulator with obs screen capture, and somehow the result is the same. weird, either this is a bug or my database is weird, or my database make KeePassDX process it as an error, not sure. Please debug it if you can.
Edit:
after reading the info button on the top left, I found no debug log method, but found this:
https://github.com/Kunzisoft/KeePassDX/wiki/File-Manager-and-Sync#synchronization-application
Does this have anything to do with my bug, or is it unrelated?
Edit: About the above statement, how do I disable 'automatic save'?
Is it the 'Autosave database' option in KeePassDX's general App settings?
Edit 3:
I get it now the content://URI should be the one below the KDBX database picker drop-down menu tab, right?
Mine is this:
content://com.android.externalstorage.documents/document/primary:KeePassMainMobile/Passwords.kdbx
Also from digging 'other-cannot-be-opened-bug type' issue, I found logfox, here is, the zipped logcat:
01_12-03-47-15_446.zip
Also, I didn't screen capture the moment but, when I try to record the logcat in my phone, the first time I try to do it. The app somehow opened my database file, but alas, it's a temporary luck or chance. It's in the bug-mode again, force closing my database.
I hope all of these are enough, if not feel free to ping/@ me, and I'll give you more needed info or logs.
The text was updated successfully, but these errors were encountered: