May 2013 - Pro-apps-dev - lists.apple.com

Re: Aperture Edit Plugin sandbox NSTask workaround?
by Rainer Standke 26 May '13

26 May '13

I am not all that experienced with any of this myself... but I wouldn't have expected this to work, because you are doing this while running in Aperture, and thus inside Aperture's sandbox, right? But hey, what works works! I have a sandboxed app in development that is set to use a user script. Here is off the top of my head how that's supposed to work: A sandboxed app has access to folder where the user can place a script that's specific to the sandboxed app. But since the user has to install / drag the script there manually, from outside the app, that is taken to be enough of a manifest user intent that the script gets to run outside the sandbox. Communication with the user script happens via passed parameters, and returned values. I plan to tell the users inside my sandboxed app to download and run an installer that would install the script for them. The nifty thing is that the script can be a unix executable, much like any command line tool. This means I even get to write this in Objective C... Just thought I'd share... (I got much of this from a WWDC video from last year, the one about scripting.) Rainer On May 17, 2013, at 14:25, Paul Miller <stelefx(a)gmail.com> wrote: > On 5/16/2013 10:42 AM, Paul Miller wrote: >> My Aperture plugin uses NSTask to launch a UI application, passing the >> image to edit on the command-line, then waits for the application to exit. >> This has worked forever, until Aperture was sandboxed. > > After two days of hair pulling and suicidal thoughts, I wanted to share with everyone my workaround for this problem. > > Instead of (the possibly much more "elegant") going with XPC services, I implemented a hair-brained workaround involving NSWorkspace, NSRunningApplication, a little "polite" polling, some NSDate checks on the file being edited, and my signed (but unsandoxed UI app). > > NSTask and waitpid don't work in the sandbox, so I had to spin until the NSRunningApplication quit. > > Here goes (error checking removed for brevity): > > // initial conditions > NSString *editedPath = ... <path to edit file> > NSString *cmdName = <path to my UI app> > NSString *appBundleID = <bundle ID of my UI app> > > // get the timestamp for the editedPath > NSError *error = nil; > NSDictionary *attrs = [[NSFileManager defaultManager] attributesOfItemAtPath:editedPath error:&error]; > NSDate *startDate = [attrs fileModificationDate]; > > // launch application using Apple events > int result = -1; > NSWorkspace *workspace = [NSWorkspace sharedWorkspace]; > [workspace openFile:editedPath withApplication:cmdName]; > > // sleep for a bit to wait for the app to start up > sleep(1); > > // now look for it based on its bundle ID (which I get from Info.plist) > NSString *appBundleID = [[bundle infoDictionary] objectForKey:@"commandID"]; > NSArray *runningApps = [NSRunningApplication runningApplicationsWithBundleIdentifier:appBundleID]; > NSRunningApplication *app = [runningApps objectAtIndex:0]; > > // poll until it quits > while (!app.terminated) > { > sleep(1); > > // spin event loop > NSEvent *event; > do > { > event = [NSApp nextEventMatchingMask:NSAnyEventMask untilDate:nil inMode:NSModalPanelRunLoopMode dequeue:YES]; > [NSApp sendEvent: event]; > } > while (event != nil); > } > > // check to see if the file has changed > attrs = [[NSFileManager defaultManager] attributesOfItemAtPath:editedPath error:&error]; > NSDate *endDate = [attrs fileModificationDate]; > > if ([startDate isEqualTo:endDate]) > [_editManager cancelEditSession]; > else > [_editManager endEditSession]; > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/lists%40standke.com > > This email sent to lists(a)standke.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Aperture Edit Plugin sandbox NSTask workaround?
by Paul Miller 17 May '13

17 May '13

On 5/16/2013 10:42 AM, Paul Miller wrote: My Aperture plugin uses NSTask to launch a UI application, passing the image to edit on the command-line, then waits for the application to exit. This has worked forever, until Aperture was sandboxed. Here goes (error checking removed for brevity): // initial conditions NSString *editedPath = ... <path to edit file> NSString *cmdName = <path to my UI app> NSString *appBundleID = <bundle ID of my UI app> // get the timestamp for the editedPath NSError *error = nil; NSDate *startDate = [attrs fileModificationDate]; // launch application using Apple events int result = -1; NSWorkspace *workspace = [NSWorkspace sharedWorkspace]; [workspace openFile:editedPath withApplication:cmdName]; // sleep for a bit to wait for the app to start up sleep(1); // now look for it based on its bundle ID (which I get from Info.plist) NSString *appBundleID = [[bundle infoDictionary] objectForKey:@"commandID"]; NSRunningApplication *app = [runningApps objectAtIndex:0]; // poll until it quits while (!app.terminated) { sleep(1); // spin event loop NSEvent *event; do { [NSApp sendEvent: event]; } while (event != nil); } // check to see if the file has changed NSDate *endDate = [attrs fileModificationDate]; if ([startDate isEqualTo:endDate]) [_editManager cancelEditSession]; else [_editManager endEditSession]; _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com After two days of hair pulling and suicidal thoughts, I wanted to share with everyone my workaround for this problem. Instead of (the possibly much more "elegant") going with XPC services, I implemented a hair-brained workaround involving NSWorkspace, NSRunningApplication, a little "polite" polling, some NSDate checks on the file being edited, and my signed (but unsandoxed UI app). NSTask and waitpid don't work in the sandbox, so I had to spin until the NSRunningApplication quit. NSDictionary *attrs = [[NSFileManager defaultManager] attributesOfItemAtPath:editedPath error:&error]; NSArray *runningApps = [NSRunningApplication runningApplicationsWithBundleIdentifier:appBundleID]; event = [NSApp nextEventMatchingMask:NSAnyEventMask untilDate:nil inMode:NSModalPanelRunLoopMode dequeue:YES]; attrs = [[NSFileManager defaultManager] attributesOfItemAtPath:editedPath error:&error];

1 0

Re: Aperture Edit Plugin sandbox NSTask workaround?
by Paul Miller 16 May '13

16 May '13

On 5/16/2013 4:01 PM, Dylan Moore wrote: Hi Paul! I don't know the specifics of what you're doing, but something that you may want to explore is XPC Services. In a nutshell, it's how you can pass data to another process space with its own entitlements. The Service that you write to process the images can then return with data, or indicate if it finished successfully. Here's why you may need this: Child processes launched by NSTask inherit the entitlements of the parent process. That's sort of how sandboxing is supposed to work, to keep malicious code from taking over a system. XPC Services can run with different entitlements, and are managed at the OS level, which dramatically mitigates risk. They're not too tough to get going, and I believe there's a lot of WWDC 2012 videos* up that talk about it. Hopefully this wasn't totally left-field, and is what you're looking for. *Here's a good one: https://developer.apple.com/videos/wwdc/2012/?id=241 Cheers, -Paul _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com Thanks Dylan for the nice summary. Yes, it does sound like the "right" way to do it. I may have a potential workaround, and if it works I'll explain later, but if that one fails I'll take a good look at XPC.

1 0

Re: launching an app with apple events and waiting for it to quit?
by Jon Chappell 16 May '13

16 May '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: launching an app with apple events and waiting for it to quit?
by George Toledo 16 May '13

16 May '13

Off the top of my head, when it comes to the opening of the app, I think the most modern way to do it would be with NSWorkspace. Something like: [[NSWorkspace sharedWorkspace] launchApplication:appPath] I think NSWorkspace may also have methods for closing the app, maybe the file stuff too? Not sure about that. I would look at the framework notes and use those methods if possible. You definitely can open/close with apple events as well, but it doesn't seem like the way that's being promoted. On May 16, 2013, at 1:42 PM, Paul Miller <stelefx(a)gmail.com> wrote: > It seems apple events may be my only option. Does anyone know how to launch an app with an "open" event, sending it a file, and then wait for it to quit, and *also* retrieve the "result code" returned by main()? > > Is that even possible? > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/gtoledo3%40gmail.com > > This email sent to gtoledo3(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: launching an app with apple events and waiting for it to quit?
by Garrick Meeker 16 May '13

16 May '13

There's probably a more modern objective-c API but take a look at Launch Services, particularly LSOpenURLsWithRole. You can get a PSN back too. Not sure about the return from main. On May 16, 2013, at 10:42 AM, Paul Miller <stelefx(a)gmail.com> wrote: > It seems apple events may be my only option. Does anyone know how to launch an app with an "open" event, sending it a file, and then wait for it to quit, and *also* retrieve the "result code" returned by main()? > > Is that even possible? > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarc… > > This email sent to garrick(a)digitalanarchy.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

launching an app with apple events and waiting for it to quit?
by Paul Miller 16 May '13

16 May '13

Is that even possible? _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com It seems apple events may be my only option. Does anyone know how to launch an app with an "open" event, sending it a file, and then wait for it to quit, and *also* retrieve the "result code" returned by main()?

1 0

Aperture Edit Plugin sandbox NSTask workaround?
by Paul Miller 16 May '13

16 May '13

This has worked forever, until Aperture was sandboxed. sandboxd: ([xxxxxx]) Application(xxxxxx) deny forbidden-sandbox-reinit Is there any way to work around this situation? Or maybe I'll just walk in front of a bus. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com My Aperture plugin uses NSTask to launch a UI application, passing the image to edit on the command-line, then waits for the application to exit. Now, because my application is not itself sandboxed, it launches (which surprised me), but my file dialogs don't work. I managed to sandbox my application, with the extra entitlement to access files in the User's home folder, but when I try to launch it from my Aperture plugin (which is also now signed), I get this error in the console:

1 0

Open source OpenCL logging tool
by Garrick Meeker 14 May '13

14 May '13

With all this recent OpenCL discussion, I'd like to mention that Digital Anarchy has just released an open source OpenCL logging and tracking tool. While it's marked as beta, I have used it with Beauty Box and it's already a useful tool. http://sourceforget.net/projects/clintercept CLIntercept inserts itself between a program and the OpenCL library. It bares a resemblance to GLIntercept or certain malloc implementations. CLIntercept can currently perform the following tasks: - Log all OpenCL calls (to a file, the console, or using NSLog). - Log only OpenCL errors. - Time all "expensive" OpenCL calls, or just the kernel execution. - List OpenCL devices and attributes (at startup, or with a separate "clinfo" executable). - Modify the devices or extensions that are returned to the program. It can also track OpenCL objects, and perform checks for leaks, mismatched calls to retain/release, situations that are not thread safe, errors with mapped images or buffers, including buffer overwrites. Any of these can be missed by the OpenCL implementation and led to incorrect behavior or even crash the system. The following are not implemented yet: - Kernel bounds checking is not implemented. (That would require a full OpenCL source code parser and preprocessor, and it's easier to modify kernel source code manually to do this.) - Detect cases where an object is referenced by a second thread before associated OpenCL commands have finished. This is not a general debugger for OpenCL kernel code. Example: For a quick demonstration you can run the test program like this: DYLD_INSERT_LIBRARIES=/my/install/path/libCLIntercept.dylib CLINT_CHECK_ALL=1 CLINT_EMBEDDED=1 ./test_clint all _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: RenderInfo scale factors are lying - FCPX only
by Darrin Cardani 10 May '13

10 May '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (mailto:Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/jasmin%40revisionfx.com This email sent to mailto:jasmin@revisionfx.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0