Synchronizing to Backblaze B2 with Cryptomator Vault -- why aren't the original modified times crossing over?

[flavorgold1]

So, I am interested in synchronizing over some folders to Backblaze B2 inside a Cryptomator Vault.

The problem is that none of the original 'modified times' are crossing over properly.

Is there some setting that I'm unaware of?

[dkocher]

This is supposed to work as we set the modification date in src_last_modified_millis metadata for the uploaded file ¹ . I couldn't reproduce this just now testing with uploading a file to a vault on B2 using Cyberduck.

Footnotes

1. 49177c8 ↩

[dkocher]

I can reproduce the problem when uploading a file using Online connect mode in Mountain Duck. The problem here is that, the metadata of the file cannot be modified after initiating the upload ¹. This is not an issue with Smart Synchronization mode where the upload is scheduled to be executed in the background only after we receive the correct modification date from the application writing the file.

Footnotes

1. https://www.backblaze.com/b2/docs/b2_upload_file.html ↩

[flavorgold1]

I wonder if there's a difference between the Windows version and the macOS version, on this issue.

[dkocher]

The issue will be reproducible on macOS in most cases unless an application sets the modification date on the file prior closing the file after write.