Skip to content

Android: Sync conflict not detected: newest copy is propagated to other clients #4305

@tomtom

Description

@tomtom

Let's say I have three devices (1 linux [A] + 2 android [B, C] if this is relevant). All devices are in sync. I switch off syncthing on all 3 devices.

  1. I edit file X on device B, then C, then A. So file X has changed on all 3 devices.
  2. I switch on syncthing on B, C, A.
  3. I wait
  4. After a while, the version of file X edited last on device A is propagated to B and C. There is not copy of the old version of X on B and C indicating a synchronization conflict.

I personally would expect to end up with at least two files indicating a synchronization conflict.

Is the situation describe in step 4 the expected outcome? Are my expectations about how synchting works wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugA problem with current functionality, as opposed to missing functionality (enhancement)

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions