Incorrect 2way sync initial conflict resolution

[ja02]

1. Create cloud folder CF1 with single file f1.txt containing ANSI text cloud (5 bytes).
2. Create local folder LF1 with single empty file f1.txt (0 bytes).
3. Create a two-way sync between CF1 and LF1 with both delete options checked.
4. Manually trigger sync process.

Error: CF1 contains files _Conflictf1.txt (0 bytes) and f1.txt (5 bytes), LF1 contains _Conflictf1.txt (5 bytes) and f1.txt (0 bytes). Next sync process causes redundant data traffic or data loss (depends on order of operations). Expected: _Conflictf1.txt and f1.txt are the same both locally and in the cloud.

[ja02]

In 2.2.2-test1 the situation is a bit better, although it takes multiple sync rounds to finish all the work. In the end, there's just a single file f1.txt both locally and in the cloud and it contains the ANSI text cloud. But, unfortunately, the local file _Conflictf1.txt, which initially appears locally, gets deleted (permanent data loss).

[ja02]

2.2.3-test4 update: When an initial conflict occurs, the conflicting file simply doesn't sync at all (nothing uploaded / downloaded).