[BUG] File Signature invalid / Either not a Keypass database or file corrupted.

Checks

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

Describe the bug you encountered:

Hello,
I have been using Keypass and Keypass2Android for 10 years+ on the following configuration :

• distant database stored on a server
• access via local or internet with Windows
• access via local or internet with android Keypass2Android

My ISP changed my static IP address, so I couldn't connect to the distant database for a while and was working on the local copy in the phone
When I discovered the static IP change :

• I mapped the reverse DNS to that address,

• I exported the local up to date database copy of my phone to the server at home

• I can successfully access it remotely with my Keypass2 Windows app

• I cannot access it with my phone that says "file signature invalid " (not a Keypass database or file corrupted).

This Looks pretty similar to this recent post on Keypass Github :
https://github.com/PhilippC/keepass2android/issues/3225
They say a bug in certain phones (Google Pixel in that case, but I run a Samsung S10e) alter the jpg files used in/as the keyfile, making the phone unable to decrypt the database.
The thing is that
1/ I only use password with no keyfile and
2/ I used to be able to decrypt it for years, and as my phone is old, there has been no OS update lately.

Any hint, please, this is annoying ?

P.S. I tried to recreate new empty databases : same, and I tried to revert to previous Keypass2android V1.14r1 instead of V1.14-Rr4, with no luck

Describe what you expected to happen:

I would expect the database to open after I enter the password

What version of Keepass2Android are you using?

V1.14r4 (tried to revert to r1 also, with no luck

Which version of Android are you on?

android 12

The report identifies Keepass2Android V1.14r4 on Android 12, with V1.14r1 also affected, but names no source file, test, or entry point. Start by reproducing the signature-invalid error with the reported local and remote database setup; done means identifying whether the failure is in file access, database parsing, or decryption and documenting a verified fix or cause.