dosya.dev
How the Desktop App handles sync conflicts
When the same file changes in two places before either change has travelled, neither version wins. Both are kept, the incoming one named with the date, the time and the device it came from, and the Issues tab tells you it happened.
- 1 Edit a file on your computer while someone edits the same file in the web app.
- 2 Note that neither change is discarded; both versions are kept.
- 3 Find your version where it was, and the other beside it, named with the date, time and device.
- 4 Check the Issues tab, which reports that the conflict happened.
- 5 Open both, keep the one you want, and delete the other.
Here’s a situation every sync tool has to answer. The same file, changed in two places, before either change had a chance to travel.
I’ll edit this file on my computer. And someone edits the same file in the web app.
So which one wins? Neither. Throwing away somebody’s work isn’t a decision a sync tool should make on its own.
Both are kept. Your version stays where it is, and the other one arrives beside it, named with the date, the time, and the device it came from.
The Issues tab tells you it happened, so you don’t find out weeks later.
Open the two, see what differs, keep the one you want, and delete the other. It takes ten seconds, and nothing was ever at risk.