-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.1107
-
Fix Version/s: 1.3.1216
-
Component/s: Direct Edit
Because then the file will exist on both sides with a different digest, and as the file history is not available it is impossible to know that only a local update has been performed since last remote update.
Yet in the case where the file has been updated server-side, the conflict is justified, but then is not handled well, as explained in NXDRIVE-122
- depends on
-
NXDRIVE-144 Drive edit: updating a file and saving it quickly creates a conflict
- Resolved
-
NXDRIVE-147 Automatically resolve self-conflicts
- Resolved