For reference and transparency: We have created this report on Apple Bug Reporter on 23 Feb 2016 here: https://bugreport.apple.com/web/?problemID=24791955
When creating a calendar by MKCALENDAR without supported-calendar-component-set, iCloud doesn’t set without supported-calendar-component-set by itself.
So the without supported-calendar-component-set property stays undefined, which means (RFC 4791):
“In the absence of this property, the server MUST accept all component types, and the client can assume that all component types are accepted.”
Steps to Reproduce:
- Create CalDAV collection with MKCALENDAR. Don’t specify supported-calendar-component-set.
- Use PROPFIND to verify that supported-calendar-component-set is not set.
iCloud doesn’t show this collection as “Calendars” and “Reminders”, but only as one of them.
CalDAV calendars without supported-calendar-component-set should show up as both “calendars” and “reminders”.
iCloud (23 Feb 2016)
direct CalDAV requests (curl/command line)
This issue behaves as intended based on the following:
The first VOBJECT - VEVENT or TODO will decide the type of this container.
Please update your bug report to let us know if this is still an issue for you.
I understand this, but I think it’s against the CalDAV specification and just wanted to report it.