I'm glad I could help with the MachServiceName, good luck with the rest. Took me many days and attempts (wiping out all certs/app ids/profiles and creating them again and again) to get something that would build and run successfully. I got it running with SIP disabled first and was able to get everything stable, it took 2 months to get approval from Apple to give my personal account the endpoint security entitlement to run with SIP enabled. The only problem I had there was that my test VM wasn't in my device list, therefore not in the provisioning profile. When I tried to run it there, it wouldn't work. Not sure of the exact error. That was a couple of weeks ago. Just look at any and all logs, all the different forums here (especially posts by eskimo), and try to read between the lines.Again, good luck!

I have these 3 settings (edited to protect the innocent) <key>NSEndpointSecurityMachServiceName</key> <string>My Bundle ID here</string> <key>NSEndpointSecurityRebootRequired</key> <false/> <key>NSEndpointSecurityEarlyBoot</key> <true/>Not sure if you need or want them all.

Thank you, Quinn. This is going onto my notes page right now 🙂

I have a question since I know almost nothing about Swift. When you create the array8 buffer by passing socketFlow.sourceAppAuditToken! into Array, is it passing the data bytes from the socketFlow.sourceAppAuditToken NSData object or the NSData object itself? I'm not sure how all this "unwraps" in Swift or exactly how you'd tell it to use the data bytes.I'm learning Swift as I go and was just wondering how it processes things like that.Thanks

Thank you, Quinn.

Hi Quinn,Yes, Xcode 11.4 beta 3 (11N132i), running on 10.15.4 Beta (19E258a)So, it's not a clock time, but a run time? I.e., it starts ticking on boot and pauses when it's asleep. I use the deadline and mach_time values to calculate a timeout value that I use to make sure we answer in time. Already had a timeout check, just updated it to use the MIN of this value (minus 1 second for a cushion) and our normal timeout value. But still occasionally see the above error message in the log after wakeup or resuming the VM after suspending it. Just made me wonder and post this question.Thanks

When you retire Quinn, 3rd party macOS development will grind to a halt 😉 No one will be able to figure out anything without your help.

Todd2,It's on my 10.15.4 Beta (19E234g) VM, not on my host 10.15.3 version. Didn't realize it until just now. But I found it through the 10.15.4 release notes originally.

I forgot to mention, I usually then do a reboot of my VM to finish removing the extension.

As mentioned above, use systemextensionsctl to uninstall it. See man systemextensionsctl for all the infoFirst, list it to see that it's runningsystemextensionsctl listThen uninstall by copying the team ID and bundle ID and running this command, with those values replacing the placeholders below.systemextensionsctl uninstall TEAMID BUNDLEID