Bug 72133

Summary: iCloud support + sync report
Product: SyncEvolution Reporter: Patrick Ohly <patrick.ohly>
Component: CalDAV/CardDAVAssignee: SyncEvolution Community <syncevolution-issues>
Status: RESOLVED MOVED QA Contact:
Severity: enhancement    
Priority: medium CC: syncevolution-issues
Version: 1.4   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 52682    
Bug Blocks:    

Description Patrick Ohly 2013-11-28 16:43:51 UTC
iCloud seems to be open to non-Apple clients now. Let's test and enhance that.
Comment 1 Jogi9990 2014-03-18 11:03:29 UTC
Did anybody manage to configure icloud?
Comment 2 Patrick Ohly 2014-03-26 16:46:40 UTC
I just gave it a try in reaction to your question.

Discovery via https://[www].icloud.com fails for various reasons.

Using one of the urls mentioned elsewhere (google "icloud caldav url") leads to a different error:

[<?xml version='1.0' encoding='UTF-8'?><error xmlns='DAV:'><Require-User-Agent xmlns='http://cal.me.com/_namespace/'/><error-description xmlns='urn:mobileme:davservices'>User-Agent Header is required</error-description></error>]

Adding a User-Agent is possible, but will require some changes to the source code. Let me know if you can and want to work on the source and I'll provide pointers.
Comment 3 Patrick Ohly 2014-10-31 07:30:51 UTC
Contacts are said to work with 1.5.

Calendars need support for downloading changes via sync reports (https://tools.ietf.org/html/rfc6578) because the current approach is not supported by the iCloud server (Apple issue 17001498 "CalDAV REPORT drops calendar data").
Comment 4 GitLab Migration User 2018-10-13 12:38:32 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/12.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.