Sadly, I don’t read Chinese, so I’m working from a machine translation of your post. I’m not entirely sure what’s going on here but, in general, Mach IPC should be able to work with any service name that’s prefixed by a valid app group ID. Now, the definition of valid app group ID has been in flux recently. I talked about that evolution in App Groups: macOS vs iOS: Working Towards Harmony. My advice here varies based on whether this is new code or code that you’ve already shipped and need to maintain compatibility with. For new code, use an iOS-style app group and have that as your Mach service name. For example, group.eskimo1.test with a Mach service name of group.eskimo1.test.my-service. Then make sure that your use of that app group is authorised by a provisioning profile. For existing code, it depends on whether this Mach IPC is entirely within your product: If this IPC is inside your product — for example, you’re communicating between two subcomponents of the same app — then you can use an iOS-s
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags: