Mountain Duck 5 Native Cloud File Versioning STILL Broken

[DanAykroyd256]

Hey,

Owned v4 for several years but never ended up using because it had many issues. Was hoping v5 would fix them to purchase again; one of them being search supposedly working now, but it doesn't; the other one, this I'm writing it here.

Simple example. I copy a new file to my OneDrive mount, when I go to the OneDrive web and check fileversion, I have two versions there; both being the same file. Needless to say, when overwriting that file with a new one, my expectation of OneDrive actually tracking the different versions I've uploaded is broken too. Now I get two different versions; both belonging to the new file I've uploaded, and the old file is lost

This is just a test.pdf I uploaded to showcase this

On the contrary, while doing the same thing with ForkLift, uploading a file over an existing one in OneDrive; when I go to the OneDrive web, I properly see only one file for each I've overwritten, as new versions. it correctly keeps tracks of each version and also doesn't duplicate them needlessly.

Could you please look into this? So far I have these two issues blocking to purchase the upgrade and trying to use Mountain Duck again.

Thanks.

[dkocher]

I can reproduce and confirm uploading files to OneDrive will cause two versions. The culprit is that we change the metadata of the file after uploading to set the correct modification date. This can be disabled in Cyberduck in Preferences → Transfers → Timstamps → Uploads. In Mountain Duck there is no configuration option as we always forward the modification date set on the file that originates from the copy process (such as macOS Finder) or the application writing the file.

I do not currently see a workaround but will check again the Graph API that is used for uploads if timestamps could be set at the time of writing the file.

[dkocher]

I have opened #17409.