Take the 2-minute tour ×

So, I'm basically in the same situation that was discussed here BUT I can't apply the proposed solution because the helper app I'm building to add to my main app bundle it's a command line executable and its own XCode project doesn't have a bundle name, embedded.provisionfile nor entitlements.

My app has been rejected two times by "not having that executable sandboxed". Well, the main app is sandboxed and the command line executable appears to be codesigned.

If I run:

$ codesign --display --verbose=4 ./myFile

I get:

Format=Mach-O thin (i386)
CodeDirectory v=20100 size=43918 flags=0x0(none) hashes=2188+5 location=embedded
Hash type=sha1 size=20
Signature size=4358
Authority=3rd Party Mac Developer Application: My name
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=08/02/2013 03:15:58
Info.plist=not bound
Sealed Resources=none
Internal requirements count=1 size=188

So I think the command is already signed. What's the proper method to sandbox and codesign this kind of file?.

share|improve this question
I have the same problem, was this problem ever resolved? –  dmid Jan 2 at 8:55
No. I ended up replacing the command file by another which had the source code available. –  rmvz3 Jan 3 at 9:11

Your Answer



Browse other questions tagged or ask your own question.