{"id":38500,"date":"2023-02-16T16:30:28","date_gmt":"2023-02-16T21:30:28","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=38500"},"modified":"2023-12-06T14:20:00","modified_gmt":"2023-12-06T19:20:00","slug":"adding-contacts-without-entitlements","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/02\/16\/adding-contacts-without-entitlements\/","title":{"rendered":"Adding Contacts Without Entitlements"},"content":{"rendered":"

David Kopec<\/a>:<\/p>\n

\n

For one-off contact additions, there’s a simpler way that requires none of that. The idea is basic: you create a contact, save it in vCard format<\/a>, and then ask the operating system to open the vCard file in the Contacts app. When the Contacts app opens, it will ask the user if they really want to add the contact. This requires no entitlements (even if you’re using the note<\/code> field), no authorization, and even works in a sandboxed app.<\/p>\n

[…]<\/p>\n

It works, but you might say, what about that note<\/code> field? If you add a note<\/code> property to your CNMutableContact<\/code> you will notice it is silently dropped when the contact is added to the address book. This has nothing to do with the note<\/code> special entitlement. It turns out CNContactVCardSerialization<\/code> does not have support for either images or the note field. You can easily add both of these back. A Stack Overflow post provides some code showing how to do so.<\/a><\/p>\n

[…]<\/p>\n

When working on a new version of my macOS app Restaurants<\/a>, I came across the note<\/code> field entitlement requirement. I submitted a request to Apple using their online form to have access to the entitlement and a week later I was rejected for my request being too vague. Fair enough, it’s their sandbox, and they have the right to reject me for being too vague. But waiting so long to get an answer was frustrating and adding contacts requires a lot of ceremony.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n