Launching executable with NSTask - Sandboxing problems?

1 down vote favorite

I have an Mac OSX application that launches a executable located in /Contents/Resources. The application is not intended to be released on App Store and so I don't have sandbox turned on. The launch code: toolPath = [[[NSBundle mainBundle] pathForResource:@"myexecutable" ofType:@""] copy]; task = [[NSTask alloc] init]; [task setLaunchPath: toolPath]; pipe = [[NSPipe alloc] init]; [task setArguments:[NSArray arrayWithObjects:@"-someArg", someVariable, nil]]; file = [[NSFileHandle alloc] initWithFileDescriptor:[pipe fileHandleForReading].fileDescriptor]; [task setStandardOutput: stderrPipe]; [task launch]; The thing is - this all works fine when running in Xcode. It also works fine when exporting the application to desktop and running it. However, if I zip the application, upload it to a webserver, and then download it on the same computer (or dropbox it to another Mac), the task no longer launches! I get no error in the system console or anything. I researched some on this problem and found that OSX will mark a new applicaton as "quarantined" special permission right. So I investigated the difference between the downloaded app and the exported app: Permissions on the executable after exporting my application from Xcode: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName At this point the app works fine and the executable is launched from a button inside the app. And after zipping the application, uploaded to server, downloaded, unzipped, and opening the application and accepting the "This application was downloaded from internet" dialogue: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName com.apple.quarantine 26 At this point nothing happens when I push the button in my app. If I then run xattr -rd com.apple.quarantine on the whole app, the quarantine notice is removed: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName but the executable is still not being launched! At this point I now have the following permissions on my desktop app: /Contents/MacOS: -rwxr-xr-x 1 Username staff 407728 21 Jul 16:31 appName /Contents/Resources: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName And on the downloaded app which I used xattr -rd on: /Contents/MacOS: -rwxr-xr-x 1 Username staff 407728 21 Jul 16:31 appName /Contents/Resources: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName The first app works fine and the second one never launches the executable. What the heck is going on? It's the same app, on the same computer, with the same permissions, but the downloaded one just doesnt work. This problem appears across all OSX versions on different computers. objective-c  cocoa share | improve this question asked  Jul 21 at 15:11 Oskar 46 3

1 Answer

active oldest votes

up vote 0 down vote accepted

I finally found out what caused this issue, it happened when trying to launch an executable with NSTask that writes files. Strangely, this works fine in some instances as mentioned in the original post. But to get it working on other computers I ended up using STPrivilegedTask which solved the problem.

1 down vote favorite

I have an Mac OSX application that launches a executable located in /Contents/Resources. The application is not intended to be released on App Store and so I don't have sandbox turned on. The launch code: toolPath = [[[NSBundle mainBundle] pathForResource:@"myexecutable" ofType:@""] copy]; task = [[NSTask alloc] init]; [task setLaunchPath: toolPath]; pipe = [[NSPipe alloc] init]; [task setArguments:[NSArray arrayWithObjects:@"-someArg", someVariable, nil]]; file = [[NSFileHandle alloc] initWithFileDescriptor:[pipe fileHandleForReading].fileDescriptor]; [task setStandardOutput: stderrPipe]; [task launch]; The thing is - this all works fine when running in Xcode. It also works fine when exporting the application to desktop and running it. However, if I zip the application, upload it to a webserver, and then download it on the same computer (or dropbox it to another Mac), the task no longer launches! I get no error in the system console or anything. I researched some on this problem and found that OSX will mark a new applicaton as "quarantined" special permission right. So I investigated the difference between the downloaded app and the exported app: Permissions on the executable after exporting my application from Xcode: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName At this point the app works fine and the executable is launched from a button inside the app. And after zipping the application, uploaded to server, downloaded, unzipped, and opening the application and accepting the "This application was downloaded from internet" dialogue: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName com.apple.quarantine 26 At this point nothing happens when I push the button in my app. If I then run xattr -rd com.apple.quarantine on the whole app, the quarantine notice is removed: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName but the executable is still not being launched! At this point I now have the following permissions on my desktop app: /Contents/MacOS: -rwxr-xr-x 1 Username staff 407728 21 Jul 16:31 appName /Contents/Resources: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName And on the downloaded app which I used xattr -rd on: /Contents/MacOS: -rwxr-xr-x 1 Username staff 407728 21 Jul 16:31 appName /Contents/Resources: -rwxr-xr-x 1 Username staff 65724 21 Jul 16:31 executableName The first app works fine and the second one never launches the executable. What the heck is going on? It's the same app, on the same computer, with the same permissions, but the downloaded one just doesnt work. This problem appears across all OSX versions on different computers. objective-c  cocoa share | improve this question asked  Jul 21 at 15:11 Oskar 46 3

1 Answer

active oldest votes

up vote 0 down vote accepted

I finally found out what caused this issue, it happened when trying to launch an executable with NSTask that writes files. Strangely, this works fine in some instances as mentioned in the original post. But to get it working on other computers I ended up using STPrivilegedTask which solved the problem.