GNOME Bugzilla – Bug 784332
EXDATE missed in recurring events
Last modified: 2017-06-29 12:14:31 UTC
This had been opened in the mailing list: https://mail.gnome.org/archives/evolution-list/2017-June/msg00074.html The issue behind this is that the Exchange server sends date-time values for EXDATE also for cases when the event time is date-only. Like here: DTSTART;VALUE=DATE:20170704 EXDATE;TZID=W. Europe Standard Time:20170704T000000 This instance is supposed to be removed from the view, but it's left there, (or can be left there), because the translation to the correct timezone moves the EXDATE one day back, to 20170703, thus it misses this instance on the 4th. There is no problem with events which are configured as no all day.
Converting EXDATE-s into date-only format fixes it. Please note that to have the calendar show correct values you either might get received an update of the event (when it changes on the server) or remove corresponding ~/.cache/evolution/calendar/<ews-calendar-uid>/ cache with closed all evolution-calendar-factory-subprocess processes (or at least the one with "--factory ews" argument). Then run evolution and the cache will re-populated, this time will show up correctly in the UI. Created commit a104115 in ews master (3.25.4+) Created commit a74b0e1 in ews gnome-3-24 (3.24.4+)