Ok here's my follow-up...I confirmed that everything I told you was true and 
finally said to myself I will just communicate with this executable inside my 
bundle.  This works until I submit it to the Mac App Store and I get invalid 
binary because this executable (3rd party) is not sandboxed.  So I give this 
binary entitlements and now when I try to communicate with it via NSTask it 
crashes and the crash report reveals that a sandbox cannot be created.  I 
thought that any of my resources carried the same sandbox anyways as my main 
app?  So now I still don't know what to do?  If I don't sandbox the executable 
it works but the App Store won't accept it, and if I do sandbox it the App 
Store (presumably) will accept it but it crashes.  What should I do?

Thanks for the help in advance as I'm quite stuck here,

rc



On Jun 23, 2012, at 3:25 AM, Nick Zitzmann wrote:

> 
> On Jun 22, 2012, at 4:51 AM, Rick C. wrote:
> 
>> Hi,
>> 
>> In the non-sandboxed version of my app upon first launch I copied a helper 
>> executable from my bundle to my application support folder (standard 
>> location) and communicated with it via nstask.  Now I'm trying to sandbox my 
>> app and I found that when I do this it fails with a read-write deny (sandbox 
>> application support location).  As a test I changed it where my app would 
>> communicate with this executable directly inside of my bundle and it seems 
>> to work.  So my question would be is this how it must be when it's sandboxed 
>> that I'm not allowed to copy resources out of my bundle into my own 
>> sandboxed application support location?
> 
> Are you sure it's copying the file into the sandboxed Application Support 
> folder and not the real one? What method are you using to discover the 
> location of the Application Support folder? The code isn't using a hard-coded 
> path to the folder, is it? Are you sure that the folder actually exists 
> before you put something into it? Would you please share with us the deny 
> error you're getting from sandboxd? Your app should have full access to its 
> sandboxed Library folder and subfolders.
> 
> Nick Zitzmann
> <http://www.chronosnet.com/>
> 


_______________________________________________

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to