Debugging sync issues with Google Drive

[alexandroid]

I am using KeepassXC on several Windows PCs and Android phones. The database file is stored in Google Drive at all times. However, periodically I notice that the passwords are missing, i.e. some passwords I know for sure I added were absent.

I fix it by going through version history of the database file in Google Drive and manually merging N past versions of the file.

However, I cannot understand why and how this happens. It makes it hard to rely on KeePassXC since I cannot tell if a password is missing or just have not been set up. Additionally, merging from past versions is a bit of a pain since UI allows me merge one DB file at a time, so I need to repeat this process for dozens of files if I don't know when the password was originally added. Just today I had to recover a password from almost a year ago this way although I knew the signup date so finding a proper revision to merge was easy.

How would you recommend troubleshooting these issues? I rarely see conflict merge messages on my phone, and I always click "merge" when I do. I am not sure which device / KeePassXC instance is causing these issues, or whether they are caused by Google Drive. I did notice Google Drive being glitchy on PCs after sleep/hibernate.

Are there merge logs generated by KeePassXC on PC and Android? Is there a way to enable some sort of a sync / merge log, if not? Is there a way to see Database stats, like number of passwords on Android? I basically need a way to catch when the number of passwords in the DB goes down, which would indicate a sync problem.

Alternatively, is there a command line tool to quickly get number of passwords in a DB file across many files (sharing the same master password), or search across multiple DB files, or export/import DB files into CSV? (as far as I can see KeePassXC CLI only works with 1-2 files at a time)

[droidmonkey]

Couple things to clarify:

• we do not have an android app, so you must be using either KeePassDX or KeePass2Android
• we do not directly sync with Google Drive, we merely write a file that drive then picks up and syncs
• you will need to reduce your variable count before we can be sure what the problem is. Make a change on one of your devices and see if that change propagates correctly (for example)
• since you are not seeing conflict files, that means (most likely) your android app is directly overwriting the kdbx file without first merging changes. This has happened to me as well in the past.

[alexandroid]

Oh, my bad - yes, on Android I am using Keepass2Android. I will direct relevant questions to it.

Makes sense on a test! I will try experimenting. The problem is that normally everything seems to work, it's only sometimes I notice the missing passwords...

And after looking to CLI docs closer, I suppose I can semi-automate my merging using some batch files. Feel free to close this.

[droidmonkey]

Might I recommend a switch to KeePassDX? It is an Android Native application versus a wrapper. It also handles merge and sync better in my opinion. That is what I use.