[Bug]: Resolve conflicts dialog (Solve sync conflicts) incorrectly identifies local vs server versions dates

[kubuntu-newbie]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Solve sync conflicts dialog incorrectly shows the date for the server version and local versions (swapping them) resulting in a wrong decision on which files to keep.
For example the server version of the file is 2 days old, the local version was modified today but the 'Solve sync conflicts' dialog shows local version as 2 days old and server version current

Steps to reproduce

restore the old backup of a user file (on a server) when there is a newer version in a folder that is being synced. the Desktop client will show 'conflict' and 'solve sync conflicts' dialog will swap the dates of the server and local files in the dialog

Expected behavior

dates for the files displayed in the 'solve sync conflicts' dialog should be correct, matching respective files

Which files are affected by this bug

any user file

Operating system

Linux

Which version of the operating system you are running.

Ubuntu 23.10

Package

Distro package manager

Nextcloud Server version

Nextcloud Hub 6 (27.1.8) snap version

Nextcloud Desktop Client version

Version 3.9.0 (Ubuntu)

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

No response

[PhilippSchlesinger]

@kubuntu-newbie The client version you use is nearly one year old and the problem you describe was solved in #5840 with corresponding PR #6043
The recent stable version is 3.12.4 (3.13.0 being just released but facing some bugs).