Re: Sandboxing. WTF?
Re: Sandboxing. WTF?
- Subject: Re: Sandboxing. WTF?
- From: Graham Cox <email@hidden>
- Date: Mon, 28 May 2012 12:44:16 +1000
On 28/05/2012, at 12:28 PM, Fritz Anderson wrote:
> On 27 May 2012, at 9:19 PM, Graham Cox wrote:
>
>> 28/05/12 12:17:01.236 PM taskgated: killed <my app>[pid 1254] because its use of the com.apple.developer.ubiquity-container-identifiers entitlement is not allowed
>>
>>
>> What does it mean, how do I fix it and how do I go about testing a sandboxed app during development?
>
> Examine your entitlements file. If the entry the Gateway daemon complains of (com.apple.developer.ubiquity-container-identifiers) is there, delete it. I assume you aren't supporting iCloud.
Ah, got it, thanks Fritz.
I'm not using iCloud. In fact I was able to simply remove the iCloud Key-Value Store and iCloud Containers in the Entitlements UI in XCode and it's running.
Sort of related question to the floor:
The only feature of my app that is really affected by this is the ability to directly browse a user's iPhoto Library. I use elements of Karelia's iMedia framework to enable this, but sandboxing thwarts it, for fairly obvious reasons (iMedia peeks directly at iPhoto's preferences and grabs resources from the common frameworks used by iWork for icons and so on, as well as going into the iPhoto library itself for images).
Our users love this feature. Has Apple given us a way to do it officially so we can keep our users happy while also toeing the line on sandboxing? If so, some pointers to that would be welcome at this point. If not, words fail me......
--Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden