Lion code-signing at all (was Re: Signing for sandboxing, etc)
Lion code-signing at all (was Re: Signing for sandboxing, etc)
- Subject: Lion code-signing at all (was Re: Signing for sandboxing, etc)
- From: Fritz Anderson <email@hidden>
- Date: Mon, 08 Aug 2011 11:39:17 -0500
On 8 Aug 2011, at 11:28 AM, Sean McBride wrote:
> Sandboxing, IMNSHO, is still half-baked. Note that on Lion, only TextEdit and Preview have it enabled. That should tell you something. I tried with my app, and hit bug after bug. In addition to limitation after limitation.
Ah. Given that we are less than three months from its being mandatory (for the App Store), that is not encouraging. I'll lay off sandboxing for the moment.
I may not have made clear in my OP that I still have a problem. I can't get my app to launch at all if it is code-signed, even if I turn off entitlements. I think I've followed all the instructions, but the instructions are ambiguous and often out-of-sync with reality. And I'm rather dense.
Code signing has been required for App Store submission for months, so I know that this part of the problem, at least, has been solved. Is there a tutorial I should be reviewing?
Here's my original posting, for reference:
> I've been trying to put a proper signature on it. I got a development provisioning profile that matches my app ID and my signing certifcate. The machine I'm running on is on the profile. It's in the Organizer. The Build Settings for the app target show the signing identity to match my certificate, which it says is pulled from the profile for the app's ID. When I run, or build for running (cmd-B), the app builds cleanly.
>
> But when I run (from Xcode or the Finder, the app is shut down immediately. This is in the Console:
>
> 8/7/11 3:22:36.402 PM sandboxd: ([68116]) taskgated-helper(68116) deny file-read-metadata /private/var/db/DetachedSignatures
> 8/7/11 3:22:36.405 PM sandboxd: ([68116]) taskgated-helper(68116) deny file-read-data /private/var/db/DetachedSignatures
>
> The stack traces go through Security::CodeSigning, among other things.
>
> Is it strange that the app would launch (just run into file sandboxing) before I got a provisioning profile?
>
> Provisioning has always been a dark art, so I'm sure I'm doing something wrong. What is it?
— F
_______________________________________________
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