KeePassDroid KDB file opens as corrupted in PC version of KeePass

[Verna Lewis]

Hello,

I have also posted this question to the KeePass forum.

I am running Windows version of KeePass 1.32 and KeePassDroid on a Google Pixel. Whenever I transfer the kdb file to my PC since getting the Pixel, the file seems to be corrupted.

While I understand that this may be a KeePass issue, I am writing to ask if anyone else has had this issue. I did not have this issue when transferring my KeePassDroid file to the PC on my prior phone, A Samsung S3 (OK don't laugh...). The file works fine on the Pixel as far as I can tell.

I get the following error information when trying to open the file on the PC:

Error code: 0x0000000A.
Invalid/corrupted file structure.

Group: 9/9.
Entry: 375/377
Meta:0.

Does anyone know if there are any diagnostics I can run on KeePassDroid on the phone to determine what the issue is? 

Thank you.

[pista...@gmail.com]

Hello,

I have the same problem.

My usage of Keepass is:

More PCs, Windows 7, 10, Keepass v 2.3.4
The database is shared over Tresorit  I am using a key file too.
LG G3, Android 5.0, KeepassDroid 2.0.6.4
Samsung Galaxy S7 edge, Android 7.0, KeepassDroid 2.0.6.4 + Keepass2Android Offline 1.01-g

Problem:
Recently I cannot read the database on Android 7.0, but I can it read on Android 5.0.
KeepassDroid 2.0.6.4:"Database format not recognized"
Keepass2Android Offline 1.01-g:"An error occured: The file signature is invalid. Either the file isn't a KeePass database file at all or itis corrupted"

I tried a few other use cases:
1) copy the database from Windows to Android 7.0 over USB MTP connection
  Result: I cannot read the db on Android 7.0
2) I have created a simple new database on Android 7.0 (Keepass2Android) and copied it over USB MTP connection to Windows.
  Result: I cannot read the db on Windows

The Samsung is a new mobile (~ 2-3 weeks old), initially had an older system than the 7.0. When I installed KeePassDroid first time on it I could read the database, I am sure.
Then the system has been upgraded to Android 7.0 and I suspect that I cannot read the db from that time, but I am not 100% sure.

Thank you.