Thanks for those answers. I have system logs from several machines that encountered this issue. Cool. Those might come in handy at some point, but I have some follow-up questions first. [quote='873693022, Retouch, /thread/813562?answerId=873693022#873693022, /profile/Retouch'] Restarting the network extension restores it immediately. [/quote] Restarting it how? By calling exit from within the NE provider? Or restarting it from the outside, like from System Settings or the provider’s container app? Beyond that, I have a question about how this problem arises. Normally one of these proxy providers works as follows: The system passes the provider’s handle-new-flow method a flow object, that is, an instance of one of the NEAppProxyFlow subclasses. The provider returns true from handle-new-flow. And kicks off any work necessary for it to proxy that flow. For example, it might open a connection to a proxy server via some networking API. Once that’s done, the provider calls one of the -openWithXyz methods on the flo
Topic:
App & System Services
SubTopic:
Networking
Tags: