"does not chuck a wobbly" is worth my annual Apple Developer cost by itself. Thank you Quinn!

I will do that and post the number. Thanks, Quinn.

Feedback # FB7526331First time I used the Feedback Assistant and not the RADAR webpage. Interesting...

I submitted the Feedback Assistant ticket on Wednesday, but haven't gotten any feedback yet. Should I have at least gotten a "thank you for your submission" message, even if it was an automated response?

Thanks, Quinn.

Hi Quinn,The man page that this leads you to says for NSEndpointSecurityMachServiceName, "If set, this string will be the name of the MachService which can be used for XPC between the ES extension and its app." Since this is no longer a LaunchDaemon app with a plist that has mach services, will this work the same and let any application connect to the ES extension via XPC? We have multiple apps that need to connect to our driver and if it's only the enclosing app that this allows, well, that'll not be good.This is on my plate to work on again next week, and it'd be nice to know before I head down a dead end.Thanks

I will share what I find when I get to that point.Thanks, Quinn

Hi Quinn and others,I tested this and yes, an external app can talk to my ES extension using XPC as if the extension was a launchd service.Looking at the man page more carefully (man EndpointSecurity), I see that at the bottom, the date is "27 November, 2018" (is it really that old?) and probably hasn't been updated for the change the release note is referencing. But that is speculation on my part.

Unfortunately no, they work in the normal case where a file besides my running binary is being opened. And I can get it to happen on just hte mmap case, no auth open event in the event subscribed list.Thanks for the idea though.

After seeing it mentioned in another post, it reminded me that I have "systemextensionsctl developer on" set. Does this affect this in any way? I'm testing with my app in the /Applications folder, so do I need this anymore?The reason I'm asking is that it didn't seem to, same loading sequence on or off.

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

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

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.

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.

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