Sync issues

Conflicts

If a file that has not been synced before by FolderSync exists both locally and remote when syncing and the two corresponding files do not have an identical modified timestamp or checksum (when available for comparison), then you will get a conflict error for the files. The same conflict will happen for a file that has been previously synced, when both the local and remote file has changed since last sync (both files get updated by your or another app with new timestamps and perhaps new content).

To handle cases where you wan't to keep the newest file you can set the conflict option on folderPair to reflect that.

If configuring a folderPair for the first time and you KNOW the files are identical on both sides, you can set "FolderPair -> Sync option -> If both local and remote file are modified" option to "Assume files are identical". This will eliminate the conflicts without re-syncing files, and update the stored sync data to reflect this. This setting should be temporary.

Potential loss of data

Only use "Assume files are identical" option as a temporary option and only if you are 100% sure the files in both local and remote folder are indeed identical.

Conflicts - one-way sync with deletion enabled

If you have sync deletion enabled in one-way sync and there are files in the target folder which wasn't synced by FolderSync they will be marked as conflicts. The V1 sync engine would just have deleted those files, but V2 as a security measure doesn't and mark them as conflicted (a default rule for C2 is that FolderSync will not delete files unless FolderSync has previously synced those files to avoid data loss).

You can override this behavior with the option "If deletion is enabled also allow deletion of non-synced files in target folder" on FolderPair sync options.