[BUG] Wrong state when saving in app, then syncing remote nextcloud.

Checks

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

Describe the bug you encountered:

Hey,

i love your app and use it at least since 1 year and enjoy it's simplicity and feature-richness.

However, in the last month i observed some weird behavior that is quite breaking the app's use case for me: When making modifications in the app and saving it to my remote keepass file (nextcloud) everything seems to work fine. First i observed vanishing entries. Then i could trigger it explicitly via clicking on "Sync database". Then it should normally look at the local copy, then at the remote and should resolve / merge the two copies. In my case it basically just says "another program modified the file, reload it". I can click on "cancel" or "ok". When i click on "ok" all my changes are deleted and i seemingly have the "old" remote copy on my app.

I tried to remove the database (including cache) but this did not work out.

I attached the debug log and one can see that there is a hash difference even if there shouldn't be one.

debug.txt

Any advice here?

Btw: It is quite risky to log username/password combinations into the debug log. I nearly uploaded it here with credentials.

Describe what you expected to happen:

Updating the remote, syncing the modified version back to my device

What version of Keepass2Android are you using?

1.09e-r7

Which version of Android are you on?

13

Start by reviewing the attached debug.txt and tracing the app's remote sync flow for the hash mismatch described when saving to Nextcloud. Reproduce the conflict on Android 13 with version 1.09e-r7; done means local changes are retained and the modified database is correctly updated remotely without exposing credentials in logs.