Our DNA is written in Swift

Calendar: Fails to update events from mail update

The CEO of the startup I am part in insists on working on a PC and scheduling our weekly jour fixe with Microsoft Exchange. I knew something was amiss because whenever he changed the time of a meeting I wasn’t able to get my Calendar entry to move.

Being a good engineer I researched the root cause and filed a bug report as rdar://18438463 and on Open Radar.


Calendar fails to update meetings from an ics file when the UID contained in the ICS file is incorrect.

Steps to Reproduce

  1. Set up a recurring meeting on Microsoft Exchange server
  2. Invite a Mac user to the meeting by email address
  3. Change one meeting occurrence to a different time
  4. The invitee receives an email containing “Mail Attachment.ics”
  5. Double-click on the ICS file and see it appear in the Calendar Inbox

Expected Results

Accepting the change via the popup from Calendar Inbox should move the meeting

Actual Results

  • First time clicking the accept button does nothing, only the entry disappears from the Calendar Inbox
  • Subsequent times there is only an OK button, again yielding no result upon clicking
  • No feedback of any sort informs the user about the problem
  • The following is logged on the console:
24/09/14 12:24:24,796 SystemUIServer[207]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior:
24/09/14 12:24:25,099 CoreServicesUIAgent[249]: Error -60005 creating authorization
24/09/14 12:24:25,125[1]: ( The _DirtyJetsamMemoryLimit key is not available on this platform.
24/09/14 12:24:25,161 CalendarFileHandler[497]: Bundle (null) does not have an FileProviderModuleClass entry.
24/09/14 12:24:25,261 CoreServicesUIAgent[249]: Error -60005 creating authorization
24/09/14 12:24:25,384 Calendar[449]: [] [Not coalescing a message we just made for event 
 because we have have replaced existing master messaged with detached: 0]
24/09/14 12:24:25,425 Calendar[449]: WARNING: Zero events found for the legacyOccurrenceID: 98842D33-29F5-4394-85A7-61C2F981C7CA/040000008200E00074C5B7101A82E00800000000701F0051086ECF010000000000000000100000002D8C849AD6240C409CAAAECEF5B49286/20140925T140000Z/-
24/09/14 12:24:25,446 Calendar[449]: Error: We are trying to open an inspector without an event.
24/09/14 12:24:30,262 CoreServicesUIAgent[249]: unexpected message <OS_xpc_error: <error: 0x7fff71c78c60> { count = 1, contents =
 "XPCErrorDescription" => <string: 0x7fff71c78f70> { length = 18, contents = "Connection invalid" }
24/09/14 12:24:30,774 CalendarAgent[233]: [] [Deleting change request because it was not materialized into a queueable operation: [<CalManagedMessageChangeRequest: 0x7fa21d303130> (entity: MessageChangeRequest; id: 0x2d000f8b <x-coredata://5BC34D0C-89AA-437A-9C8B-B7B3E25B1942/MessageChangeRequest/p180> ; data: {
 dependencies = "<relationship fault: 0x7fa2187830a0 'dependencies'>";
 dependents = (
 eTag = "";
 error = nil;
 firstMaterialized = nil;
 localUID = nil;
 materializedCount = 0;
 principalUID = "002DD2CA-AC2F-47D4-AACF-10B96964F711";
 scheduleTag = nil;
 sequenceNumber = 180;
 serverFilename = "Local_Managed_Message_7C8294D6-342B-4340-A620-DB6756BDF88A.ics";
 sharedUID = nil;
 sourceUID = nil;
 type = 18;


I narrowed the problem do a non-matching UID value in the ICS file. Workaround:

  1. mail the recurring event from Calendar
  2. this gives you an ICS file which upon inspection shows the correct UID value of the calendar event
  3. Modify the “Mail Attachment.ics” file, correcting the UID value
  4. With the updated UID the expected results occur, the single meeting occurrence is moved.

I have no idea why the UID is incorrect. If this is an issue in Microsoft Exchange Server, then still I expect Calendar to be resilient enough to find the correct meeting if no matching UID exists.

Categories: Bug Reports

1 Comment »

  1. Всем привет кто ищет знакомства то тут очень много именно симпатичных девушек и не только, всем парням советую!!!!!!!