Repeated saving to Dropbox fails with "No such file" about keepassium HOT 4 CLOSED

Finally found out the cause and fixed the issue. Apparently, new Dropbox fails to handle NSFileCoordinator.coordinate() calls that include both the reading and writing intent simultaneously. This is likely their bug but it can be solved on KeePassium's side, too.

The fix is coming with the next update.

from keepassium.

Hmm, this is a tough one… I have tried many variations of the file writing parameters and found only one that seemingly solved the problem: removing file coordination. If the app simply writes to the file without any regard to other app, the database in Dropbox can be written several times without an issue. Not really a fix, but good enough for a quick patch.

As the patch was heading to the App Store, I discovered that file changes are indeed saved to the file, but that file never gets uploaded to Dropbox. Dropbox simply does not detect the file as modified, so all the changes remain in device's local cache. So the problem actually became worse.

Sorry, folks. Patch release postponed, we go back to square one…

from keepassium.

Looks solved case with create-save-edit-save record on v1.46.140 beta.

from keepassium.

@LVladymyr, thank you for confirming.

from keepassium.