Don't hold your breath for a new API. Apple does not want sandboxed apps to communicate with each other except through extremely limited means: OS X Services (which is limited to static Services only) and what appears to be a one-way mechanism defined under Mtn Lion (not sure what part of it is under NDA and what part was covered in news articles).
An Apple engineer claims the above is not true, but when I asked for a clarification on exactly how sandboxed apps were to communicate with other apps, I never got a response. This appears to not be just some blip, but is intentional and unlikely to change. I also filed bugs against this issue, which were closed and dubiously moved to "internal tracking" after months of no response. It was later determined that there is no intention of every allowing any kind of access to usability APIs from a sandboxed app. So they were apparently to afraid to just come out and say it, but instead used "internal tracking" option for the same effect. Mark On Fri, Feb 17, 2012 at 10:30 AM, Patrick Robertson <robertson.patr...@gmail.com> wrote: > I've also filed a bug at least 3 months ago, and it appears Apple have been > ignoring it. I have come to the same conclusion as you on the matter Nick. > > It seems we must either wait for a new API (which I think is unlikely to > happen) or have to remove features that rely on this from our applications. > > Thanks for your reply Nick, it's nice to know that I'm not the only one. > > On 17 February 2012 18:27, Nick Zitzmann <n...@chronosnet.com> wrote: > >> >> On Feb 16, 2012, at 1:22 AM, Patrick Robertson wrote: >> >> > As a follow up, it appears that in 10.7.3 Apple have included a further >> > Console log message along the lines of: >> > >> > 16/02/2012 08:12:28.319 sandboxd: ([23644]) WebProcess(23644) deny >> > hid-control >> > >> > >> > It appears that Sandboxed applications do not allow external applications >> > to run the AXUIElementPostKeyboardEvent anymore. >> > >> > Do people consider this to be reasonable/make sense? Somehow, I don't see >> > how it's justifiable for a Sandboxed app to display this behaviour, and >> > causes serious usability problems. >> >> I have a bug filed on this, but I don't think Apple's ever going to allow >> use of the accessibility API or event posting from the sandbox. According >> to what I've read on the forums, allowing apps to do that is a >> sandbox-defeating security hole. Sandboxed apps aren't allowed to use >> NSAppleScript or AESend() to communicate with the outside world for the >> same reason. They get temporary exceptions, but the "temporary" means they >> might be taken away... >> >> 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/unmarked%40gmail.com > > This email sent to unmar...@gmail.com -- Mark Munz unmarked software http://www.unmarked.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
