Skip to content

Instantly share code, notes, and snippets.

@hjuutilainen
Created November 19, 2013 11:47
Show Gist options
  • Star 8 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save hjuutilainen/7544223 to your computer and use it in GitHub Desktop.
Save hjuutilainen/7544223 to your computer and use it in GitHub Desktop.
Log messages by Fantastical (OS X)
19.11.2013 13.41.32,403 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,403 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,406 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,406 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,406 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,407 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,409 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,409 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,410 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,410 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,412 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,412 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,424 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,425 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
19.11.2013 13.41.32,425 secd[540]: securityd_xpc_dictionary_handler Fantastical[1799] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
19.11.2013 13.41.32,425 Fantastical[1799]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
@hansmestrum
Copy link

Hi there,

I see these messages a lot in my console on my mac What does that mean?

@jayallen
Copy link

Ditto here. I just sent them a support email and included a link to this gist as well, so hopefully we'll hear back soon

@joshuakarjala
Copy link

please post update - just found the same here

@jayallen
Copy link

Just got word back from Fantastical's support team. I'm sure they won't mind me copying it here:

These messages are a bug in Maverick's calendar frameworks. For the most part they can be ignored, but they are really annoying to see showing up in the console so much. We've made some changes to reduce the amount of logging that Fantastical triggers, but it still does print some errors. Hopefully a lot less than 400 an hour though!

He also said that there's an update pending approval in the App Store which will resolve the issue.

@fearoffish
Copy link

I still get errors, although a slight different message. Do you?

@Metasequ0ia
Copy link

I experience the same: lots of fantastical messages in the log. there was an update to 1.3.12 a few days ago. but still enormous logging activity...

@tvachon
Copy link

tvachon commented Jan 31, 2014

I'm seeing the same log activity as well...

@stuartcw
Copy link

Just noticed them today..

@michaelaye
Copy link

This is how many I get within 2 minutes!!

https://gist.github.com/michaelaye/9775386

And this kind of burst happens every 7-10 minutes!
Too many for my taste, will pause using Fantastical for now. Is there more information about this general calender framework bug somewhere? Did somebody complain in a blog somewhere publicly? Is Apple aware of it?

@jarus
Copy link

jarus commented Apr 5, 2014

I'm seeing the same log entries. Is there any news about this "bug"?

@catesandrew
Copy link

Just saw this message on Wireload

After upgrading to Mac OS X Mavericks (10.9) you may see many messages like this in your System Log (Console.app > System Log):

03/01/2014 10:46:00.554 secd[26594]: securityd_xpc_dictionary_handler Blotter[99146] copy_matching The operation couldn’t be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)

03/01/2014 10:46:00.554 Blotter[99146]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))

This is a known problem with Mac OS X Mavericks that affects many sandboxed apps (any app sold on the Mac App Store) using calendar functionality.

We raised the issue with Apple when Mavericks was still in Developer Preview.

Apple is aware of the issue and they are working on a fix. In general Apple does not make promises about specific timelines for bug fixes but we are hopeful this issue will be fixed by the forthcoming Mac OS X 10.9.2 update.

So looks like blame could be on Mavericks

@krackers
Copy link

krackers commented May 7, 2022

As you guys noted, this indeed seems to be an apparent bug in Maverick's calendar framework, which seemingly persisted all the way until maybe 10.10-ish. You can see slightly more info about the root cause in soffes/SAMKeychain#88 but essentially calling into CalendarStore indirectly ends up invoking keychain via the following stack trace


  * frame #0: 0x00007fff8b2b4a43 CalendarPersistence`-[CALKeychain loadKeychainInformationsForURL:realm:login:shouldDeleteEntry:] + 127
    frame #1: 0x00007fff8b2b46b6 CalendarPersistence`+[CalDAVAccount passwordWithScheme:login:host:path:port:] + 136
    frame #2: 0x00007fff8b31b5a7 CalendarPersistence`-[CalManagedCalDAVAccount retrievePasswordWithoutHavingPrincipalWithURLRegistered:] + 177
    frame #3: 0x00007fff8f4bf59d CalendarStore`+[CalGroup(CreationFromManagedObject) groupFromManagedObject:] + 1232
    frame #4: 0x00007fff8f4c65f8 CalendarStore`-[CalCalendarStore(CalCalendarStore_Private) calendarsWithPredicate:] + 595

Theere's a call to SecItemCopyMatching in loadKeychainInformationsForURL where the query dictionary has sync set to 1, which is appears to be what causes this based on the linked github issue. I can confirm that if this is set to 0 (e.g. by modifying value in lldb) the error no longer occurs, but even then it doesn't actually find any matching keychain entries (the SecItemCopyMatching call returns error not found) and so the method itself returns nil, so it doesn't seem like the method return value is actually used in any meaningful capacity.

And indeed, if we investigate what it's used for, the result is basically used to populate an object CalGroup which might be like CalGroup <0xfoobar> {UID = 1111-11123123-123123123; title = Google; type = CalDAV}. If a valid password was returned, it'd be part of the key/values, but if nothing was returned it's left out of there. And the clincher is that this CalGroup isn't even used in any meaningful sense since it's the calendars themselves we care about.

The various calendarstore methods eventually end up calling [CalCalendarStore calendarsWithPredicate], which basically does something like

// fetch all managed objects
for each idx in list:
   cal = CalCalendar calendarFromManagedObject:idx];
   if [idx group]
       group = [CalGroup groupFromManagedObject:idx];
       [cal setGroup: group]

so the password for the calendar group isn't even really relevant here, since all we care about is the grouping info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment