Message Could not load database #1933
Comments
|
Can you still open the database with KeePassXC, with the previous version of KeePassDX or some other KeePass-compatible software? Have you tried opening the kdbx file the other way around i.e. from your file manager? A likely cause of failure could be an invalidated internal path. Did this happen right after the update or after some edits? Do you have older versions of the database that still can be opened? |
|
I was able to open the database with a Keepass compatible app. I was using the Android file picker to attempt to open the file with KeepassDX and it was not working. I just tried to open the file from another location using google drive and it failed with the same message. |
|
I am able to open the database with all other compatible applications on Windows, Android and Linux. I have been using this database for years and have it stored in multiple locations. |
|
This happened after the update to Android 15 and Nothing OS 3.0 beta |
|
Is there a log file I can access somewhere on Android that may be able to help? As I mentioned I am able to open the database with another app but I would prefer to use KeepassDX. |
|
I apologize for the late response. |
|
You can install LogFox from F-Droid to access the system logs or you can access them using adb from a computer connected via USB (https://developer.android.com/tools/logcat). The latter is more complicated. |
|
I have Fdroid. let me see if I can do that. |
|
okay that isn't the most intuitive thing I have ever done but I used ADB with the Ubuntu terminal and I believe I was able to get the message from that. org.chromium.content.app.SandboxedProcessService0:0} If that's not all you need you may have to give me the command here to paste into the terminal. That would be much easier. |
|
I ran the following command adb logcat ActivityManager:I MyApp:D *:S Then I opened the app. It failed to open the database and the code above displayed in the terminal. |
|
If you use adb with USB debugging, the following command should be sufficient in your shell: Then try to open the database and see what log messages you get. There should be a couple of dozens lines. There should be nothing sensitive in there except for the filepath. |
|
There's a lot more than a dozen lines. Do you want me to post all of it? Or is there a certain section you are interested in? |
|
Here it is. 11-21 14:52:58.001 3092 3100 W ndroid.systemui: ApkAssets: Deleting an ApkAssets object ' and /data/app/~~ZlngIiPpsj-SzwPPLXKDzg==/com.kunzisoft.keepass.free-nYNyS6npnUkYW8vWS3TIkQ==/base.apk' with 2 weak references |
|
and BTW it also does not open with the password. |
|
There seems to be a problem with the dates, perhaps an unrecognized format is causing the error, I had done quite a bit of testing but perhaps an exception capture is missing. I'd have to reproduce the problem with a database that doesn't contain sensitive data. I'll investigate. |
|
@BigCityCat: Could you create a dummy database with the same tools and way you used for the affected database and see if it causes the same issue? @J-Jamet: Could you provide a build that logs the timestamps which cannot be parsed (hex encoded)? |
|
@BigCityCat Could you also have a look with KeePassXC and see what timestamps are shown in Database -> Statistics. Database created and Last saved. In my case they look like this: Which is actually not my format of choice. |
|
I created a new dummy database and it opened fine but it may be impossible to create it exactly the same way. I'm using Flatpak now. This database was created years ago. I use all fields. Passwords, URL and notes |
|
I'm not sure if this will help. I'm using a FlatPak App called Secrets. And on the phone keepassdx.
|
|
I will log into windows and see what that app says. |
|
In theory, you could sort the entries in KeePassXC by Last Modified date and go through all the entries until you find some nonsensical date. I wonder if an extra leap second (a minute with 61 seconds) could cause this problem. |
|
KeepassXC |
|
actually there are quite a few that say 12/31/1969 7:00 PM and I see some that have creation dates in the future actually 2025. I was not alive in either of those. maybe I can go back and modify the dates. But After dinner. |
|
"12/31/1969 7:00 PM" might not be what's actually in the decrypted XML, but the result of not being able to parse the timestamp. I don't think you can edit the timestamps of the entries with KeePassXC. What you can do is clone them without the history and delete the original entry. The new entry will have the current time for all timestamps. I'm not quite sure whether it's a great idea that KeePassDX won't open the database at all if there's a bogus timestamp. I'd prefer if it threw a warning and opened the database read-only, at least. |
|
I was actually able to go through and delete the history on some and others I just made a small adjustment and saved it so the date was updated. After I moved the file back to my phone and it did open. It's fixed. Thanks for your help. |
|
Hopefully I was able to help improve your app in some way. Appreciate your commitment. Thank you. |
I agree with that. Thanks guys for investigating, I'll create a new rule to not throw the exception to prevent opening but replace with the current date if impossible to parse. |
Describe the bugTrying to open database that has been used for years. App doesn't open with password or biometric. Message Could not load database.
A clear and concise description of what the bug is.
To ReproduceAttempt to open database.
Steps to reproduce the behavior:
Expected behavior
database to open
KeePass Database
KeePassDX:
Android:
Android 15
Nothing Phone 2
Nothing OS 3.0 beta
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: