On 6 Aug 2011, at 4:28 PM, Fritz Anderson wrote:
> I have an NSPersistentDocument, with autosave-in-place enabled. When I try to
> save the document after editing it, it balks with both application-modal
> alerts and document-modal sheets, all with generic messages about being
> unable to create or save the document.
Okay, I tracked this down to Lion sandboxing. If I remove my signature and the
entitlements from the app, it saves just fine.
But I want to be sure sandboxing works, so 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 (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
