[BUG] New databases instantly 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:

• I made a new database using the OEM Keepass 2.x 64-bit Windows application (latest release), saved to my Google Drive. I can open and edit this database in the OEM Keepass application.
  I cannot open this new, default/unedited database in Keepass2android - I get a notification the database may be corrupted.

The reverse gives trouble too.

• I create a new database using Keepass2android, saved to my Google Drive. I can open and edit this database in Keepass2android.
  I cannot open this database in the OEM Keepass application, it gives a database corruption error.

Describe what you expected to happen:

Just like in the past, I'd expect flawless operation on both keepass2android and the OEM Keespass application regarding the database.

What version of Keepass2Android are you using?

1.11-r0

Which version of Android are you on?

Android 14 (stock, not rooted)

No source file or test is named. Start by reproducing database creation and opening in both KeePass2Android 1.11-r0 on Android 14 and the OEM KeePass 2.x Windows application, using Google Drive storage; done means a newly created database from either application opens and can be edited in the other without a corruption warning.