Process exceptions of recurring events



  • Unfortunate missing feature. I’ve first investigated caldav sync adapter which has exactly the same issue. But my work calendar is full of exceptions and so also davdroid is pretty much useless to me 😞
    I’d propose this is something for the FAQ.



  • Hey, there - same problem with my
    Evolution <-> Owncloud <-> Davroid <-> Android

    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.

    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.


  • developer

    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.

  • developer

    Results of today’s reading:

    • The recurring “master” event and all its exceptions share the same UID. The exceptions have a RECURRING-ID that shows which of the event instances is overriden by the exception.
    • All VEVENTs with the same UID (i.e. the master event + its exceptions) have to be in the same .ics file on CalDAV servers.


  • Hello,
    I am also willing to make a donation for this enhancement (and for full support of the iCalendar RFC). As far as I am concerned this bug unfortunately makes DAVdroid completely unusable!


  • developer

    Can you try with 0.7.3 (will be in the stores soon, or download here: https://github.com/bitfireAT/davdroid/releases/download/v0.7.3/davdroid_0_7_3.apk)?
    Please also read https://davdroid.bitfire.at/faq/entry/recurring-events


  • developer

    I am also willing to make a donation for this enhancement (and for full support of the iCalendar RFC).

    BTW: While testing, I haven’t seen any working implementation with full support of the iCalendar RFC, even iCloud fails and crashes if you play around too much in the Web GUI (just try adding a recurring event, then moving around single instances, deleting them, switching between all-day and date-time, etc.).


  • developer

    Basic support has been implemented with 0.7.3. For mre specific issues, please create a new ticket with verbose information.



  • well, what would you need?
    I installed git HEAD yesterday (reading the release notes), and even removed the account and re-created it…
    but exceptions are still not handled correctly.

    (eg. a recurring event that has a few dates removed is still shown all the time.)


  • developer

    Please provide detailed instructions on how to reproduce in a separate issue. Please also read https://davdroid.bitfire.at/faq/entry/recurring-events


Log in to reply