#1483 Corrupt File - Android 5.x - Windows 10???

[Dirk Demeuth]

I am using a Android 5.1 Smartphone with "KeePassDroid" 2.0.4 and on my PC "Kee Pass Password Safe" V. 2.31.

After changing listings at my smartphone, the kdbx-file couldn't open on my PC, because it is corrupt. The file could open on the smartphone after changeing and safeing on the smartphone.

On my androd-tablet also with "KeePassDroid" 2.0.4 the same file couldn't also open.

Where is the problem? What about Android 6.x?

Regards

[Dirk Demeuth]

Add:

The android-tablet got android V 4.4.2

Created or chageing files on windows10 PC could be open also on tablet and smartphone

[wellread1]

Data corruption is a multicausal phenomenon. Your configurations includes many potential sources, including disruption during synchronization e.g. synchronization during device shutdown or entering sleep; a defect in the synchronization routine of the third-party post of KeePass (KeePassDroid); errors in internet data transmittal; errors on the unspecified cloud storage service; etc. Unless you can define a set of conditions that can be used to reproduce the issue its hard to treat this as a KeePass bug.

The reason you can open the database on your phone but not other devices is that the cached working copy of your database on the phone is OK and it is likely isolated by synchronization from the corrupt database located on the cloud server.

Your database on your android-tablet probably probably doesn't have a cached copy of the database so it is affected by the corrupt cloud copy. Alternatively it is the source of the database corruption. Likewise your have likely configured KeePass so that the working copy of your database on your PC is probably the corrupt cloud copy.

To recover:

It may be easiest to recover a slightly older, good copy of your database from the cloud service directly e.g. Dropbox has a previous versions feature, other service may have similar features. Once you synchronize the older good copy with the current good copy on your phone, all databases will be up-to-date. You can also recover the good cached copy from your android phone. If you don't know how to do that you might want to ask on the KeePassDroid forum or other general purpose android forum.

To further mitigate the inconvenience of database corruption in the future:

Make regular backups of your database.

Configure KeePass so that a local copy of your database (outside of the cloud service) is you working copy and synchronize that local copy with your cloud copy. You can automate the process with a trigger. It is difficult for file corruption to cross a synchronization barrier. If it does cross, that would probably indicate that synchronization is the point of corruption.

---

If you can identify a reproducible method to create database corruption during synchronization, that would be very helpful.