XCode 15 does not recognize device with usb behind a corporate proxy (macOS 14)

Question

I work behind a corporate proxy connected via Cisco Anyconnect. When I am not connected to the VPN, XCode 15 does recognize my physical iPhone which is connected via cable. As soon I switch to the VPN, XCode loses the connection. It seems XCode tries to connect only via Wifi as soon I am in the corporate network. Which is weird because the finder recognizes the device via cable and without a VPN connection it works fine too.

Under "Manage run destinations" I find the following message for my iPhone:

Internal logic error: Connection was invalidated
Domain: com.apple.CoreDevice.ControlChannelConnectionError
Code: 1
User Info: {
    DVTErrorCreationDateKey = "2023-09-28 08:17:11 +0000";
    "com.apple.dt.DVTCoreDevice.operationName" = enablePersonalizedDDI;
}
--
Transport error
Domain: com.apple.CoreDevice.ControlChannelConnectionError
Code: 0
--
The connection was interrupted.
Domain: com.apple.Mercury.error
Code: 1000
User Info: {
    XPCConnectionDescription = "<RemoteXPCPeerConnection 0x600002c8eda0> { <remote connection: 0x6000033b7200> { type = rsd, state = not-connected, remote service name = com.apple.internal.dt.coredevice.untrusted.tunnelservice, server mode = 0, protocol version number = 1, protocol feature flags = 0x6, local service version = 0, remote service version = 2, traffic class = 0, (root, reply) helo received = (1, 1), next msg id = 9, first msg id = 3, send in progress = 0, preexisting socket = -1 }";
}
--


System Information

macOS Version 14.0 (Build 23A344)
Xcode 15.0 (22265) (Build 15A240d)
Timestamp: 2023-09-28T10:17:11+02:00

This issue exists since the update to macOS 14, it worked fine before. Anyone with the same issue or a solution?

Pompano

I have met the same problem before, after I change my VPN to V2Ray, it is be resolved. I designed a custom rule to bypass apple and my company, which means direct to connect. – Harassed

Answer 1

My IT department just succeeded in the Herculean task of getting both Cisco and our VPN provider to admit the problem existed and was caused by the VPN, and got Cisco to provide a solution that our VPN provider had to implement. VPN settings are definitely not my strong suit, but he sent me this excerpt from Cisco's docs to explain the problem:

Configure IPv4 or IPv6 Traffic to Bypass the VPN

You can configure how the AnyConnect client manages IPv4 traffic when the ASA is expecting only IPv6 traffic or how AnyConnect manages IPv6 traffic when the ASA is only expecting IPv4 traffic using the Client Bypass Protocol setting.

When the AnyConnect client makes a VPN connection to the ASA, the ASA can assign the client an IPv4, IPv6, or both an IPv4 and IPv6 address.

If Client Bypass Protocol is enabled for an IP protocol and an address pool is not configured for that protocol (in other words, no IP address for that protocol was assigned to client by the ASA), any IP traffic using that protocol will not be sent through the VPN tunnel. It will be sent outside the tunnel.

If Client Bypass Protocol is disabled, and an address pool is not configured for that protocol, the client drops all traffic for that IP protocol once the VPN tunnel is established.

For example, assume that the ASA assigns only an IPv4 address to an AnyConnect connection and the endpoint is dual stacked. When the endpoint attempts to reach an IPv6 address, if Client Bypass Protocol is disabled, the IPv6 traffic is dropped. If Client Bypass Protocol is enabled, the IPv6 traffic is sent from the client in the clear. If establishing an IPseç tunnel (as opposed to an SSL connection), the ASA is not notified whether or not IPv6 is enabled on the client, so ASA always pushes down the client bypass protocol setting.

You configure the Client Bypass Protocol on the ASA in the group policies.

Irreducible