Post

Replies

Boosts

Views

Activity

Reply to Defining two XPC services in a single System Extension
OK. My next step here would be to check whether launchd knows that the sysex is allowed to publish that service. You can do that with launchctl: Under a section with my bundle ID, I see: $(TEAMID).$(BUNDLEID) = { 				active count = 3         copy count = 0         one shot = 0         path = (submitted by smd.290)         state = running         program = /Library/SystemExtensions/063E252D-C01E-4EBE-96F5-1C5FA0650106/$(BUNDLEID).systemextension/Contents/MacOS/$(BUNDLEID)         arguments = {                 $(BUNDLEID)         }         default environment = {                 PATH => /usr/bin:/bin:/usr/sbin:/sbin         }         environment = {                 XPC_SERVICE_NAME => $(TEAMID).$(BUNDLEID)         }         endpoints = {                  "group.$(APP_BUNDLEID).content-filter-service" = {                          port = 0xb0ba7                         active = 1                          managed = 1                          reset = 0                          hide = 0                  }            } ... } So I see the Mach service for the content filter only. The service I had defined for the plist key NSEndpointSecurityMachServiceName is not available. It also follows a different naming convention though, $(TEAMID).$(BUNDLEID).xpc. Not sure if that matters.
Sep ’20