Nextcloud Files displays wrong "Modified" date after reading/closing a Collabora file without making any modification

[RodSeq]

Describe the bug
When I read a file with latest version Nextcloud 27.0.1 + Nextcloud Office 8.1.1 + Collabora CODE 23.05.2, then close the file without making any modification to the file: Nexcloud Files always wrongly displays that the file has been modified "seconds ago". Refreshing the page, Nextcloud Files always displays the correct latest modification date & hour of the file.

To Reproduce
Steps to reproduce the behavior:

1. Open a file with Nextcloud Office + Collabora CODE.
2. Close the file without making any modification to the file.
3. Check the "Modified" column: Nextcloud Files always wrongly displays that the file has been modified "seconds ago"

Expected behavior
When I read a file using Nextcloud Office + Collabora CODE then close the file without making any modification, Nextcloud Files should always display the latest modification date & hour in the "Modified" column

Server details

Database: 10.5.21
PHP version: 8.1.21
Nextcloud version: 27.0.1.2
Version of the richdocuments app: 8.1.0
Version of Collabora Online: 23.05.2

[rotdrop]

I have the same problem. Actually, I think the point is here that the file actually is saved by the app although it has not been modified. So the bug is not that the underlying core services do something wrong, but that the file is actually written. I have verified this, and also that the generated versions are actually byte-by-byte identical.

This is a bit annoying as it also means that the versions file space is polluted with "ghost-versions" with no change which just consume space on the server.

[rotdrop]

... I actually just read that my issue seems to be different as NC actually does save the unmodified file and generates new versions. @RodSeq: can you verify that in your case really no new versions of the file are generated and the file isn't actually saved? Because in my case the file is actually written to disk and in my server logs I see

... "POST /index.php/apps/richdocuments/wopi/files/18588_ocbnl45ljkp9/contents?access_token=... "COOLWSD HTTP Agent 23.05.2.2" 

which means that the "code"-server is actually requesting a putFile() when closing the unmodified document.

[chris-meyer3]

Same problem here in NC 28.0.1 (and earlier 27.x).

[...] "POST //index.php/apps/richdocuments/wopi/files/23834_ocqyqx2tl9sg/contents?access_token=[...]&access_token_ttl=0%2Fws%3FWOPISrc%3Dhttps%3A%2F%2F[...]%2F%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F23834_ocqyqx2tl9sg&compat= HTTP/1.1" 200 1675 "-" "COOLWSD HTTP Agent 23.05.7.2"

[chris-meyer3]

Any progress on this issue?
TNX

[joshtrichards]

Related: #2771

#2771 (comment)

[chris-meyer3]

There is some progress.

The situation is different today. Most recently, all office applications were affected by the incorrect date. Today, only the file formats of the 'calc' application seems to be affected.

Wrong file date:
*.ods
*.xsl, *.xlsx

Correct file date:
*.odt
*.odp
*.doc, *.docx
*.ppt, *.pptx

[Nextcloud Hub 8] (29.0.8)
Collabora Online - Built-in CODE Server - Version 24.4.902

[chris-meyer3]

Same behavior in NC 30.0.3 + Collabora 24.4.1002

[juliusknorr]

@chris-meyer3 That is an interesting finding. I think we move this report over to https://github.com/CollaboraOnline/online as the place where the change of the file is triggered.

Could you file an issue over there?

FYI @pedropintosilva