syncthing conflicts when modifying calendar on different devices
Opened this issue · 9 comments
Hi,
I am trying yo use DecSyncCC and Syncthing to share a calendar for several people.
It seems everything is fine if one adds a calendar entry, then sync with the other devices.
The problem seems to be when adding an entry in one device that is offline, and the calendar is modified in a second device before the first device could go online and sync.
From that time, there are conflict files in DecSyncCC folder created by syncthing, and calendars couldn't be merged.
At first glance I thought it was a Syncthing issue, so I searched in its GitHub page.
I found a similar issue and the answer was that Syncthing will never manage a merge strategy
I wonder if someone found this issue as well and if there is any way to get this working....
Thanks!
Just for reference, I'm using Android, and here is the link to that syncthing issue I found:
syncthing/syncthing#4831
Supporting this use case is an explicit goal of DecSync, so it is a bug of DecSync CC and not of Syncthing. It should just work fine and no file conflicts should be created.
Could you share the conflicting files with personal information removed? And the device models and Android versions? It would be a problem when you share the calendar between two identical devices (I should fix this). As you mention that you share it with several people, this could be the case.
Here is a zip with DecSync folder of two devices, named Android1 and Android2.
Both are Nokia 6.2 with Android 10.
I used sed to remove personal information.
Hope this helps!
decsync.zip
It is indeed what I expected. It doesn't work well right now when synchronizing between two identical devices, which is a bit stupid. But I am surprised it works at all. I would expect that events won't be synchronized, unless there is a third device that creates or modifies the event. When both collections are enabled and you create an event on one device, will it show up on the other device?
By now, it doesn't happen because of the conflicts. Do you know how can I resolve the conflicts without loosing data? I only tried with these two devices.
When I first tried, the answer was yes, the event showed up in the other device. I can try again once the conflicts are resolved.
Both devices had the same Android name. Now one has changed. Is this important?
What can I do so they look different so DecSyncCc works right?
I think I fixed the issue, and it should work fine in the next version. In your case, you have to reinstall one of the applications to make it work, once the update is available.
Perfect! Do you know when this new version is scheduled?
Thanks!
I just want to test a few changes before publishing it. It is planned in a few days, but it will also take a few days after that before it is available on F-Droid.
After having some really hard time, where the calendar entries weren't doing the initial syncing at all on latest version. Downgrading to 1.3.0 fixed it and after updating again, everything works fine.
Commented here as I think this has to do with syncthing issue, having a syncthing folder which get changes from same single device but from different ROMs.