[BUG] K2A claims every database is corrupt

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

For a few weeks I've been having issues with Keepass2Android;
1st login attempt on any database results in error: "The file signature is invalid. Eith..." (abbreviated, full message not shown)
2nd and following login attempts: "The file signature is invalid. Either the file isn't a KeePass database at all or it is corrupted.
I am sure it's the correct file 'database.kdbx', as I use it on PC and on Mac as well, it's synchronized through Google Drive to all my devices.

Due to this issue persisting on Keepass2Android, I created a new database, and imported the 'old' database using the official KeePass windows software (on which no corruption is mentioned by the way) The new database is called 'DBv2.kdbx'. For a few days it's worked on K2A, but now it also claims corruption upon opening.

No issues have occurred on Windows or OSx that would result, as far as I can tell, in any corruption. It is only Keepass2Android that claims any form of corruption. I mainly use K2A for copying and pasting credentials on my smartphone, as I mainly use generated passwords that are impossible to remember and a hassle to copy from another screen.

What can I do or test to diagnose and fix this issue?

Describe what you expected to happen:

Start Keepass2Android, open database and get access to credentials.

What version of Keepass2Android are you using?

1.10-pre

Which version of Android are you on?

14

Start by reproducing the failure in Keepass2Android 1.10-pre on Android 14 with both database.kdbx and DBv2.kdbx, then compare opening the same files on Windows or macOS. Done means determining why valid databases are reported as corrupt, or capturing enough diagnostic evidence to identify the failing step.