We are implementing a Transparent Proxy for HTTPS (via TCP and QUIC). The following rules are set in startProxy: settings.includedNetworkRules = [ NENetworkRule(destinationNetwork: NWHostEndpoint(hostname: "0.0.0.0", port: "443"), prefix: 0, protocol: .TCP), NENetworkRule(destinationNetwork: NWHostEndpoint(hostname: "::", port: "443"), prefix: 0, protocol: .TCP), NENetworkRule(destinationNetwork: NWHostEndpoint(hostname: "0.0.0.0", port: "443"), prefix: 0, protocol: .UDP), NENetworkRule(destinationNetwork: NWHostEndpoint(hostname: "::", port: "443"), prefix: 0, protocol: .UDP) ] Handling TCP connections seems to work fine. But opening UDP flows from Chrome (or Brave) always fails with Error Domain=NEAppProxyFlowErrorDomain Code=2 "The peer closed the flow" (Doing the same for Firefox works!) BTW: We first create a remote UDP connection (using the Network framework) and when it is in the ready state, we use connection?.currentPath?.localEndpoint as the localEndpoint parameter in the open method of the flow. Is it a known issue that QUIC connections from Chrome cannot be handled by a Transparent Proxy Provider?

I'm trying to build an macOS App that has a MainView (containing a list of selectable items) and an InspectorView (to get more info about the selected item) on the right. I would like to have: The InspectorView should be "togglable" (in best case using animations), i.e. there is a "hide/show inspector" toggle button, that should expand/collapse the InspectorView (this resizes the window). If the InspectorView is shown, there should be a divider between the two views to resize the views (-> split view) If the InspectorView is shown, resizing the window should first resize the InspectorView (up to a minimal width) (-> .layoutPriority) I thought I could make it work by using a NavigationView. But I failed with 1. Is there a way to get 1. with a NavigationView as well, or should I use different views? (I couldn't get it to work with a HSplitView either.) Note: The window is created in an NSApplicationDelegate.