Project

General

Profile

Bug #652

Broken recurrences are not synchronized correctly with EAS and DAV

Added by Luca Gasparini 5 months ago. Updated 5 months ago.

Status:
New
Priority:
High
Assignee:
-
Start date:
01/15/2019
Due date:
% Done:

0%

Estimated time:
Affects Version:
5.5.0
Fix Version:
Release Version:

Description

If you delete an event of a recurrence from the mobile at the next synchronization, the deleted event appears again.
The problem is present both using CalDAV and EAS

If you delete an event of a recurrence from the web interface on the mobile you will not delete the event only if you use CalDAV (with EAS being deleted)

Steps to reproduce:
- create a recurrence using the web interface
- synchronize the mobile device using both CalDAV and EAS
case 1: delete a recurrence event from the mobile and force synchronization
case 2: delete a recurrence event from the web interface

Expected behaviour:
case 1: the deleted event does not appear in the calendar
case 2: the deleted event does not appear in the calendar

Actual behaviour:
case 1: the deleted event appears again after synchronization with both CalDAV and EAS
case 2: the deleted event appears again after synchronization only using CalDAV (with EAS it remains deleted)

History

#1 Updated by Luca Gasparini 5 months ago

In addition to what has already been described:

- if from the web interface the time of a single event of the recurrence is changed (by breaking the chain) on the mobile device the moved event appears twice (both in the recurrence and the new one moved)

Also available in: Atom PDF