Bug - synchronising folders with existing content does not sync modified files at all

[hotchkj]

The Filen desktop client does not appear to always take file modification times (or, in extremis, checksums) into account when synchronising files. This is noticeable when setting up sync across two machines with folders that have existing content (a very likely scenario when migrating from an old sync app to Filen).

Steps to reproduce:

1. Machine 1: Install Filen, create folder A and set up sync with desktop client e.g. test.txt
2. Cloud: test.txt is present in folder A with modification time from step 1
3. Machine 2: Create folder A, create test.txt with a later modification time than Machine 1's copy
4. Machine 2: Install Filen, set up sync with the same cloud folder A

Expected results:

• Latest test.txt is uploaded from Machine 2
• Machine 1 receives latest test.txt

Actual results:

• Filen reports sync is successful but no actual data is changed
• Cloud folder A is unchanged with old test.txt
• Machine 1's folder A still contains old test.txt
• Machine 2's folder A still contains latest test.txt

It is necessary to go through the entire file list by hand and resolve the disparity manually. This dramatically erodes trust in the storage, since I have to check each and every file is actually in the cloud at the modification time I expect.

Thanks for your attention.

OS: Windows 10 x64 App: v2.0.24