You should read this post, which has a detailed explanation of how to approach this issue.
Note That post assumes you’re using
NSXPCConnection
, which is something I recommend in general. If you use the low-level XPC API, you’ll have to map from high-level constructs to low-level constructs. For example, the
processIdentifier
property maps to the
xpc_connection_get_pid
function. If you have any questions about that mapping, let me know.
Finally, you wrote:
XPC client should have specific bundle identifier
It’s best to avoid the bundle identifier here and look at the code signing identifier or, better yet, test a code signing requirement that includes the identifier. The code signing identifier is canonical way to identify code. Normally it’s aligned with the bundle identifier but that’s not guaranteed.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"
—
WWDC runs Mon, 4 Jun through to Fri, 8 Jun. During that time all of DTS will be at the conference, helping folks out face-to-face.