Re: Sandboxing and calling Launchctl

2012-06-24 Thread Rick C.
This helped me thanks! Unfortunately I wasn't try to launch my helper app via launchd so it was a bit different. But had to say thanks! :-) rc On Jun 1, 2012, at 9:30 AM, Alex Zavatone wrote: > If you haven't watched the video for Session 204 - "App Sandbox and the Mac > App Store" from th

Re: Sandboxing and calling Launchctl

2012-06-01 Thread Roland King
On Jun 1, 2012, at 4:33 PM, Mark Allan wrote: > Thanks Alex, > > Thanks for your reply. > > If you're talking about the com.apple.security.inherit entitlement, that only > works for helper apps which are launched via fork/exec from the main > application. When the helper app is launched by L

Re: Sandboxing and calling Launchctl

2012-06-01 Thread Mark Allan
Thanks Alex, Thanks for your reply. If you're talking about the com.apple.security.inherit entitlement, that only works for helper apps which are launched via fork/exec from the main application. When the helper app is launched by LaunchServices (via SMLoginItemSetEnabled) it crashes immediat

Re: Sandboxing and calling Launchctl

2012-05-31 Thread Alex Zavatone
If you haven't watched the video for Session 204 - "App Sandbox and the Mac App Store" from the WWDC 2011 videos, there might be some info in there that will help you around the 9 minute mark. Search for the 2011 WWDC videos on developer.apple.com GL, - Alex Zavatone On May 31, 2012, at 6:35

Re: Sandboxing and calling Launchctl

2012-05-31 Thread Mark Allan
On 29 May 2012, at 15:42, Mark Allan wrote: > For anyone following, using temporary entitlements only gets rid of two of > the four errors, so I still can't make scheduling via launchd work. > > sandboxd still spits out: > launchctl(14634) deny job-creation > > and Xcode/run log still giv

Re: Sandboxing and calling Launchctl

2012-05-29 Thread Mark Allan
For anyone following, using temporary entitlements only gets rid of two of the four errors, so I still can't make scheduling via launchd work. sandboxd still spits out: launchctl(14634) deny job-creation and Xcode/run log still gives: launch_msg(): Socket is not connected Other

Re: Sandboxing and calling Launchctl

2012-05-29 Thread Torsten Curdt
> SMLoginItemSetEnabled can be a solution. Again "fabulous" documentation on that one. I tried my best to get the usual "start on login" wrapped up in a helper https://github.com/tcurdt/TCLoginItemHelper ...but in the end just left it out of the app. cheers, Torsten _

Re: Sandboxing and calling Launchctl

2012-05-29 Thread Mark Allan
On 29 May 2012, at 12:24, Stephane Sudre wrote: > On Tue, May 29, 2012 at 10:52 AM, Mark Allan > Hi all, >> >> I posted this to the developer forums yesterday but I think this list >> probably gets a good bit more eyeball than the forum, so I'm sending here >> too. Sorry for the cross-post if y

Re: Sandboxing and calling Launchctl

2012-05-29 Thread Stephane Sudre
On Tue, May 29, 2012 at 10:52 AM, Mark Allan wrote: > Hi all, > > I posted this to the developer forums yesterday but I think this list > probably gets a good bit more eyeball than the forum, so I'm sending here > too. Sorry for the cross-post if you're seeing it twice.  Anyway... > > I'm trying

Sandboxing and calling Launchctl

2012-05-29 Thread Mark Allan
Hi all, I posted this to the developer forums yesterday but I think this list probably gets a good bit more eyeball than the forum, so I'm sending here too. Sorry for the cross-post if you're seeing it twice. Anyway... I'm trying to put together the last bits and pieces of sandboxing my app bu