When an exception is added to a recurring event and is being synced to a server by DAVdroid, the exception is not properly reflected on other clients like Owncloud web client and Thunderbird Lightning. The same can be observed the other way around: When an exception is created by Lighning, it is not properly reflected on an Android calendar synced by DAVdroid.
The following software has been used to reproduce the issue:
- Android 4.2.2
- DAVdroid 0.8.1
- Owncloud 8.1
- Lightning 4.0.1
The following problems arise:
Procedure: Create an event exception on Android, sync using DAVdroid.
Outcome: The exception is not visible in the Owncloud web client, the event is still there. The event is still listed in Lightning with a strike-through effect:
Expected result: The event should not be visible on the date the exception was made for, neither in Owncloud nor Lightning.
Procedure: Create and sync an event exception using Lightning.
Outcome: The exception is reflected in the Owncloud web client (the event is gone on that date). On Android+DAVdroid, the event is still present on the date the exception was made for and does not show any kind of alteration.
Expected result: The event should not be visible on the date the exception was made for, neither in Owncloud (matches the Outcome above), nor Android (where DAVdroid seems to fail integrating the exception properly).