I was under the impression that the fault recovery part was the reason why you were suggesting running an executable.
XPC was the thing I found, when I was looking for ways to execute code and communicate with it from my host app. But now I understand that compiling loading a dynamic library is the way to go.
That's how I will start, and then probably run all of that in an XPC Service, for fault recovery.
Regarding executing the compiled code from a sandboxed app: You were mentioning the com.apple.security.files.user-selected.executable entitlement. This would be exactly what I need, right? But it is almost never allowed by the App Store Review team? What is a way to find out? Submit the app and see?
This leads me to my original question again. Could I distribute a Mac app in the App Store, and then have users install an additional, non-sandboxed app from a website, which launches a MachService? Would my sandboxed app be able to talk to that MachService? Or is this forbidden by the system?
In other words: Is there any change to build what I want to build, and distribute it through the App Store?
Thank you again for your help!
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags: