Hey, there - same problem with my
Evolution <-> Owncloud <-> Davroid <-> Android
Yes. Exceptions for recurring events are simply not implemented at the moment (when receiving them in an iCalendar).
But the second, in my opinion relating, problem seems to be, that whenever I delete one instance of the recurring event, davdriod seems to create a second instance of this event with the exception.
No. This second event with the exception is created by the Android Calendar Provider (see how DAVdroid interacts with the Calendar Provider).
What is the actual state of this bug, because its a big problem for me.
In the actual version I simply can’t use this really great app.
The status is that handling of exceptions is not implemented yet, neither when receiving iCalendars nor when collecting events from the Calendar Provider.
I guess that this work would be necessary:
- CalDAV server → Calendar Provider: If an iCalendar contains a VEVENT with a recurring event and other VEVENTS with exceptions, these exception events should be added to the Calendars Provider as an exception (related to the recurring event).
- Calendar Provider → CalDAV server: Exceptions for recurring events in the Calendar Provider should not be treated as normal events but associated to the recurring event; one iCalendar with recurring event + exceptions should be created instead of two separate iCalendars.