Thank you very much for your reply! It would be great if you could clarify some things for me:
and for a named XPC endpoint vended by a launchd daemon you use init(machServiceName:options:).
I believe this is what I did, see my second code example (machServiceName: ...). I'm wondering why it didn't work.
it’s feasible to compile your code to something that’s loadable (a Mach-O dynamic library or bundle) and then have your XPC service load that.
What is the benefit of loading the dynamic lib from the XPC service, and not from the main app directly? Overall stability for cases where the lib crashes?
Or would this somehow allow me to distribute my editor app through the App Store? AFAIK it is not allowed for a sandboxed app to compile code, is it? And a XPC service distributed with my sandboxed app is also sandboxed, correct?
I understand that loading the dynamic lib has a lot of benefits regarding security and stability, but I'd like to understand if it is a absolute requirement.
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags: