When an event has a date-time DTSTART, but a date EXDATE like this one:
# generated by Evolution
DTSTART;TZID=Europe/Vienna:20240317T100000
RRULE:FREQ=WEEKLY;UNTIL=20240526T080000Z;BYDAY=SU
EXDATE;VALUE=DATE:20240331
it's currently imported to Android as EXDATE:20240331T000000Z and then erroneously shown in the calendar.
Regardless of whether such an EXDATE/RDATE is technically valid, DAVx5 should detect the type mismatch and set the correct type internally to behave like users would expect.
When an event has a date-time DTSTART, but a date EXDATE like this one:
it's currently imported to Android as
EXDATE:20240331T000000Z
and then erroneously shown in the calendar.Regardless of whether such an EXDATE/RDATE is technically valid, DAVx5 should detect the type mismatch and set the correct type internally to behave like users would expect.