This is surprising to me as the CLI works perfectly fine when signed with a development certificate and provisioning profile, both when automatically signed by xcode and manually signed with a development cert.
So what is not supported? CLI system extension activation in general or just Developer ID signing for it?
mjgalindo
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Thanks! I'll give that a try/
I've now confirmed that if I change the plist file CFBundleExecutable to the ApplicationDaemon instead of the ApplicationClient, then the ApplicationDaemon runs fine with the profile uninstalled, but the client does not, requiring the profile to be set if I want entitlements to work for it.
Well, it was supposed to look like this
<key>CFBundleExecutable</key>
<string>ApplicationClient</string>