Database file not syncing through Dropbox

[Android-X13]

After I installed KeePassDX, I opened my already existing database file from the Dropbox storage and everything was fine (all entries were as expected).

However any changes I make through KeePassXC on my computer do not reflect in KeePassDX. For example I created a "Test" entry via KeePassXC, saved/closed the database, made sure that Dropbox picked up the changes in the db file, and then opened KeePassDX on Android but the entry has not been added.

Dropbox is connected and working in both machines, Internet connection is working. I also verified though Keepass2Android, which immediately picked up the changes and the Test entry was visible.

What I tried:

• Reloading the database from inside KeePassDX
• Merging the database from inside KeePassDX
• Manually removing the database from KeePassDX history and re-opening it
• Deleting KeePassDX cache
• Deleting KeePassDX data

But the Test entry is never shown.

On the other hand if I make a change via KeePassDX and save the database, this is reflected in KeePassXC on the computer.

KeePassDX 3.3.1 (libre build from F-Droid)

[J-Jamet]

Duplicate : #1235

https://github.com/Kunzisoft/KeePassDX/wiki/File-Manager-and-Sync
#840
#342

The problem comes from the Dropbox application. Clear the cache of this application.

[Android-X13]

Hi @J-Jamet. Clearing Dropbox cache doesn't work, nor does clearing the cache + force stopping the app and then opening it again. Marking the file to be available "offline" and then opening that one in KeePassDX also doesn't work. I guess if I uninstall and re-install the Dropbox app it will probably work but I won't try it.

So my understanding is that Keepass2Android uses proprietary Dropbox API to circumvent this problem, is that correct? If yes then it's good that you don't implement it... as long as there is some way to make cloud/remote sync work.

I'm having trouble following some of the info laid out in the Wiki page and some tickets that you linked though. Is SyncThing the only viable solution?

[J-Jamet]

So my understanding is that Keepass2Android uses proprietary Dropbox API to circumvent this problem, is that correct? If yes then it's good that you don't implement it... as long as there is some way to make cloud/remote sync work.

Yes. The solution to using proprietary cloud services that do not properly implement their file provider is to create a separate file manager application that implements the API. Kunzisoft/FileSync#5