Hacker News new | ask | show | jobs
by dav- 3858 days ago
I'm not really an OSX developer, but shouldn't it be possible to bypass the sandbox in a way by offering the user to install an unsandboxed auxiliary application via a download from your website which then communicates with the main sandboxed App Store application using some protocol and performs any actions which the MAS version would be otherwise unable to?

For example, perhaps the auxiliary application runs a local HTTP server with a REST API. The MAS application simply makes HTTP requests to the auxiliary application such as `POST /applescript/doStuff`.
1 comments
ThomPete 3858 days ago
Against Apple Terms I believe. They will ban you if they find out.

I was talking with apple support and they basically said that if we even offered some extra component to get rid of the spinning gear we would most likely be banned.

link
vsl 3858 days ago
> Against Apple Terms I believe.

Citation of the specific term needed. It isn’t against any of them and plenty of apps do it (Things, Boom or Monity come to mind). Apple requires that the app is functional without extra downloads and the app itself must not download the extra executables. But it’s OK to use them for extended functionality (Things: system-wide popup; Monity: extra sensors) as long as you only point the user to where to download the extra helper and they do it themselves (see e.g. http://www.monityapp.com/helper/ for one such helper download page, linked from in app).

link
ThomPete 3858 days ago
Bypassing the Sandbox is not extending the capabilities.
link
mh- 3858 days ago
I'm pretty sure this is exactly what Boom 2 does.

https://itunes.apple.com/us/app/boom-2-best-audio-enhancemen...

Note their reference in the description to an 'optional component' that enables system-wide effects.

link