Highlights
🐛 remoted is no longer left suspended when a tunnel fails to start (macOS)
On macOS, remote start-tunnel / tunneld briefly SIGSTOP Apple's remoted while an iOS 17+ RSD tunnel is being established, then resume it. If establishment failed partway — entering the CoreDevice service context or starting the QUIC/TCP tunnel raised — remoted was left suspended, and a stopped remoted persists after the process exits, breaking Xcode / devicectl / Finder device access until it is manually resumed or the machine reboots. The establishment window is now guarded so remoted is always resumed, even on error.
📚 Documented why the RSD path suspends remoted
docs/guides/network-stacks.md now explains the real reason start-tunnel/tunneld suspend remoted — contention for the device's RSD RemoteXPC endpoint over the USB NCM link — and dispels the long-standing (incorrect) assumption that it was caused by the device closing the host's fd during pairing.
What's Changed
- 980cc10 remote: never leave remoted suspended if tunnel establishment fails (#1873) (@doronz88)
- 0eeb095 docs: explain why the RSD path suspends remoted (#1872) (@doronz88)
Full Changelog: v10.11.4...v10.11.5