Hi,
The following appointment works fine in InfCloud and Android, but it doesn't show up on iPad. Is there anything wrong with it?
BEGIN:VEVENT CREATED:20141201T101916Z LAST-MODIFIED:20141202T084819Z DTSTAMP:20141202T084819Z UID:855afabb-e5a8-42b8-9e54-395bd598b9f1 SUMMARY:****** RRULE:FREQ=WEEKLY;UNTIL=20160101T093000Z;BYDAY=MO,TH;WKST=MO TRANSP:OPAQUE CLASS:PUBLIC DTSTART;TZID=Europe/Amsterdam:20150105T103000 DTEND;TZID=Europe/Amsterdam:20150105T113000 DURATION:PT1H END:VEVENT
-- Johan
Hi Johan,
Technically this VEVENT violates RFC5545 https://tools.ietf.org/html/rfc5545#section-3.6.1. DTEND and DURATION are mutually exclusive, only one may appear NOT both (or neither).
On 01/29/2015 05:19 PM, Johan Vromans wrote:
Hi,
The following appointment works fine in InfCloud and Android, but it doesn't show up on iPad. Is there anything wrong with it?
BEGIN:VEVENT CREATED:20141201T101916Z LAST-MODIFIED:20141202T084819Z DTSTAMP:20141202T084819Z UID:855afabb-e5a8-42b8-9e54-395bd598b9f1 SUMMARY:****** RRULE:FREQ=WEEKLY;UNTIL=20160101T093000Z;BYDAY=MO,TH;WKST=MO TRANSP:OPAQUE CLASS:PUBLIC DTSTART;TZID=Europe/Amsterdam:20150105T103000 DTEND;TZID=Europe/Amsterdam:20150105T113000 DURATION:PT1H END:VEVENT
-- Johan
Not sure if that's the actual reason, but the event has DTEND and DURATION , which is invalid. These properties are mutual exclusive.
Marten
Am 29.01.2015 um 14:19 schrieb Johan Vromans:
Hi,
The following appointment works fine in InfCloud and Android, but it doesn't show up on iPad. Is there anything wrong with it?
BEGIN:VEVENT CREATED:20141201T101916Z LAST-MODIFIED:20141202T084819Z DTSTAMP:20141202T084819Z UID:855afabb-e5a8-42b8-9e54-395bd598b9f1 SUMMARY:****** RRULE:FREQ=WEEKLY;UNTIL=20160101T093000Z;BYDAY=MO,TH;WKST=MO TRANSP:OPAQUE CLASS:PUBLIC DTSTART;TZID=Europe/Amsterdam:20150105T103000 DTEND;TZID=Europe/Amsterdam:20150105T113000 DURATION:PT1H END:VEVENT
-- Johan
On Thu, 29 Jan 2015 14:28:11 -0800 Marten Gajda marten@dmfs.org wrote:
Not sure if that's the actual reason, but the event has DTEND and DURATION , which is invalid. These properties are mutual exclusive.
Apple is known to be picky, so this may very well be the reason this appointment does not show on iPad.
How to reproduce:
Create the appointment using CalDAVzap or InfCloud: duration 2hours, repeating weekly on MO and TH for some time (e.g. until 31-12-2015). The appointment now has only DTEND.
On Android, modify the appointment, all occurrences, from 2hrs to 1hr.
Now it has both DTEND and DURATION.
Could this be a problem of the Android CalDAVsync app?
-- Johan
Yes, that's probably a CalDAV-Sync issue. Android requires a DURATION for recurring events. Of course the DTEND should be removed in that case. Is that our CalDAV-Sync or the other one? I'll check our code and fix it if necessary.
cheers
Marten
Am 29. Januar 2015 23:36:07 PST, schrieb Johan Vromans jvromans@squirrel.nl:
On Thu, 29 Jan 2015 14:28:11 -0800 Marten Gajda marten@dmfs.org wrote:
Not sure if that's the actual reason, but the event has DTEND and DURATION , which is invalid. These properties are mutual exclusive.
Apple is known to be picky, so this may very well be the reason this appointment does not show on iPad.
How to reproduce:
Create the appointment using CalDAVzap or InfCloud: duration 2hours, repeating weekly on MO and TH for some time (e.g. until 31-12-2015). The appointment now has only DTEND.
On Android, modify the appointment, all occurrences, from 2hrs to 1hr.
Now it has both DTEND and DURATION.
Could this be a problem of the Android CalDAVsync app?
-- Johan
On Fri, 30 Jan 2015 07:10:56 -0800 Marten Gajda marten@dmfs.org wrote:
Yes, that's probably a CalDAV-Sync issue. Android requires a DURATION for recurring events. Of course the DTEND should be removed in that case. Is that our CalDAV-Sync or the other one? I'll check our code and fix it if necessary.
Yes, it's your CalDAV-Sync.
Thanks for looking into it.
-- Johan
Hi Johan,
please tell me which Android version (or Custom ROM) and which calendar app you use. You can reply off-list to marten <at> dmfs.org
cheers
Marten
Am 30.01.2015 um 17:20 schrieb Johan Vromans:
On Fri, 30 Jan 2015 07:10:56 -0800 Marten Gajda marten@dmfs.org wrote:
Yes, that's probably a CalDAV-Sync issue. Android requires a DURATION for recurring events. Of course the DTEND should be removed in that case. Is that our CalDAV-Sync or the other one? I'll check our code and fix it if necessary.
Yes, it's your CalDAV-Sync.
Thanks for looking into it.
-- Johan
-
Johan Vromans -
Ken Murchison -
Marten Gajda