Hello, I have encountered the same problem you have described. I can fairly easily reproduce it on a MacBook running M1 Pro chip, but we are having difficulties reproducing it on intel Macs. I am therefore thinking it might have something to do with additional security checks Macs on arm might do.
System restart usually fixes this issue. Killing the extension and/or client which tries to connect to it does not help.
capso
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
Last seen
User for
Post
Replies
Boosts
Views
Activity
the issue seems to be fixed in beta 4 :)
Yes, that is exactly what is happening. I will submit a bug.
some additional information: running systemextensionctl list shows the extension in "Activated disabled" state
meanwhile, is there any method (in swift/obj-c) to get the actual system extension status?
This could help as well. Found this error while poking around in debug. The connection to service on pid 0 named {team identifier is here}.com.example.apple-samplecode.SimpleFirewall.SimpleFirewallExtension was invalidated.edit:running systemextensionsctl listshows no systemextension running.