Hi Darian,
there aren’t any errors in the log and the behaviour is what I would expect from Z-Push.
@darian said in Completing recurrent tasks breaks sync:
I created a task “RecurrentTask” with due date 28.10.2018 and a weekly recurrence.
In the log it’s starting on the line 92. The client sends a request to create a new recurring task “RecurrentTask” with the id 2762 (line 95, I’m using the client ids here and below as they’re numerical and easier to follow). Kopano creates a new recurring task with the id Ufdaea:4df90d90836a4cf9afab484e55ac2d35231907000000 which the client use from now on to identify the task.
@darian said in Completing recurrent tasks breaks sync:
I completed the task and got 2 tasks in Kopano, the initial one and a recreated duplicate with new due date next week.
The client creates two new tasks with the same subject “RecurrentTask” with the ids 2763 (line 570) and 2764 (line 647) and removes the task 2762 (line 712) you’ve created in the first step. Tasks 2763 represents the completed one (Kopano id Ufdaea:4df90d90836a4cf9afab484e55ac2d35251907000000). Task 2764 is the new recurring tasks with the due date one week later (Kopano id Ufdaea:4df90d90836a4cf9afab484e55ac2d35261907000000).
@darian said in Completing recurrent tasks breaks sync:
Then I renamed the task on my phone to “RecurrentTask-renamed”. This renamed the initial task in Kopano only.
The client actually renamed the new recurring task (2764) only (line 1557). The completed task 2763 remained untouched.
@darian said in Completing recurrent tasks breaks sync:
Finally I deleted the task on my phone which deleted the initial task in Kopano but left the recreated task untouched.
In the log it looks like the remove request was issued on the mobile client, but nevertheless it was like in the previous step for the task 2764 only (line 2324).
I hope this explains what’s going on and that the Z-Push behaviour is actually as it should.
Manfred
