Skip to content

VirtualHere and USB Network Gate with Xcode: why the iPhone drops, and what works

By Taha Yasin KucukPublished Updated 4 min read

Share the cable with Xcode: try Nuticast

Short answer: USB-over-network tools such as VirtualHere and USB Network Gate forward raw USB from one computer to another. That works for many devices, but developers keep reporting the same two problems with an iPhone and Xcode: the phone shows up in the USB tool but not in Xcode, or it connects and then drops. Since iOS 17, Xcode doesn't talk to an iPhone over plain USB anymore. It reaches it over network services (RemotePairing and a CoreDevice tunnel) that run on top of the cable. If the phone is plugged into a Mac, it's more reliable to forward those services instead of the USB device. That's what Nuticast's USB sharing does.

The setup this is about

The iPhone is cabled to one computer, and Xcode runs on another:

  • a test phone plugged into a Mac mini in a rack or a cupboard,
  • a phone on a teammate's desk,
  • your Mac at home, while you work from somewhere else.

You want Xcode on your Mac to build, install and debug on that phone as if the cable were yours.

What developers run into

The reports follow a pattern:

  • The phone is listed in the USB tool, but Xcode doesn't see it. One VirtualHere user describes exactly that (forum thread).
  • The connection drops right away when the device sits on a remote Mac (forum thread).
  • Setups that worked before iOS 17 stopped working. A remote Mac that used to see local devices could no longer find an iOS 17 phone after the Xcode 15 update (Apple Developer Forums).

None of this means the tools are bad. They forward USB well. The problem is what Xcode expects to find at the other end.

Why it happens

Since Xcode 15 and iOS 17, Xcode uses Apple's CoreDevice stack. When an iPhone is plugged in, it brings up a small network link over the cable (USB-NCM), and Xcode reaches the phone through services on that link: remotepairingd checks the pairing, then a tunnel (QUIC over UDP) carries installs, launches and the debugger.

A USB-over-network tool has to recreate that whole USB device on the other computer, including its network interface, with the timing intact. Each extra layer is another chance for the RemotePairing handshake or the tunnel to time out. When one does, Xcode simply doesn't list the phone, or marks it offline.

A route that skips USB forwarding

If the computer with the cable is a Mac, you don't need to forward USB at all. The phone already offers RemotePairing and its tunnel on the cable's network link. Forward those ports over the network, and tell Xcode on your Mac where to find the phone, and Xcode connects the same way it does locally.

That's how Nuticast's USB sharing works:

  1. On the Mac with the cable, switch on USB Sharing (or run nuticast share). It finds the phone's RemotePairing port and forwards it, plus each tunnel port Xcode asks for, from one of that Mac's network addresses.
  2. On the Mac with Xcode, add the phone with the USB via computer connector and the other Mac's address, then start the bridge.
  3. Xcode lists the iPhone as a normal run destination. Run, breakpoints, LLDB and the console work as usual.

The phone needs no Wi‑Fi and no VPN. The two Macs need to reach each other, ideally over a mesh VPN such as Tailscale, so the forwarded ports aren't open to a whole office network.

Side by side

USB-over-network toolNuticast USB sharing
What it forwardsThe whole USB deviceThe network services Xcode uses (RemotePairing, CoreDevice tunnel)
Computer with the cableMac, Windows, Linux, NASA Mac running Nuticast, or a Windows PC running Nuticast USB Host
iPhone shows up in XcodeOften reported missing or droppingAs a normal run destination
Phone needs Wi‑FiNoNo
PairingThrough the forwarded USBPaired once with the Xcode Mac, next to it
Other USB devicesYes, anythingNo, iPhone and iPad only
CostPaidFree on the Mac with the cable; a license on the Xcode Mac

If you need to share printers, dongles or Android phones too, a USB-over-network tool is still the right kind of product. For an iPhone and Xcode, forwarding the services is the shorter path.

Common questions

Can Xcode use an iPhone plugged into another Mac without extra software? No. Xcode only sees devices on its own Mac's cable or Wi‑Fi. You need either a remote-desktop session to the other Mac, so Xcode runs there, or a tool that brings the phone to your Mac's Xcode, such as Nuticast's USB sharing.

Does the phone have to be paired with my Mac first? Yes, once, while it's next to your Mac (over Wi‑Fi on iOS 27 or later, or over a cable). After that it can live on the other Mac's cable.

Does the Mac with the cable need a Nuticast license? No. Only the Mac that runs Xcode and starts the bridge needs one.

Does this work if the computer with the cable runs Windows or Linux? Windows: yes. Nuticast USB Host runs on the Windows PC with the cable and forwards the iPhone to your Xcode Mac; see the Windows host. Linux isn't supported. The computer with Xcode is always a Mac.

Written by Taha Yasin Kucuk

The iOS developer who builds Nuticast, answers its support mail and writes every guide on this site. If a step does not match what you see, write to hello@nuticast.com.

GitHubAbout NuticastChangelog

Try it. Pairing is free.

Bridging needs a license on the Xcode Mac: $49 per year, with a 14-day refund if it does not work for your setup. Requires macOS 13.5+, Xcode 15+ and iOS 17+.

Download for MacSend this to my MacShares the download link with your Mac.See pricing
More guides