Comment 33 for bug 888504

The issue described in comment 28 and comment 29 is a different issue. This bug is for reading the date fron the iCloud server.

What you describe by "if I trie to assign an existing event to an other icloud calendar, if I understand correctly is that you change the calendar in the event modification dialog box and press ok. If that is the case then I think this is more an iCloud limitation than a Lighting bug.

From what I remember, when changing the calendar of a meeting, Lighting will issue simultaneously a PUT in the new calendar and a DELETE in the old calendar to delete the meeting from the old one and create it in the new one, there might be a short time during which the meeting exists in both calendars at the same time. The server error message "... with same UID in a different collection" seems to indicate that iCloud has the limitation of not supporting a meeting with the same UID in a different calendar (which is valid per CalDAV rfc). Workarounds could probably be implemented on the client side to support this. In any case a new bug should be open to track this different issue.