@SwiftBeginner2026 Thanks for checking. Configurator being able to read the device information makes a basic USB connection problem less likely. However, it doesn’t confirm that Xcode’s development connection is working, and pairingState: unsupported alone isn’t enough to identify the cause.
There are a few more checks you can try without resetting your iPhone:
1. Confirm that Terminal is using the same Xcode installation you have open.
Run:
xcode-select --print-path
xcodebuild -version
xcrun --find devicectl
Compare the version and build with Xcode > About Xcode, and check that the paths point into the expected Xcode installation. If they don’t, select the correct version under Xcode > Settings > Locations > Command Line Tools, then run xcrun devicectl list devices again.
This helps ensure the command-line results actually correspond to the Xcode version you’re troubleshooting.
2. Check for VPN or network-filter interference.
If you use a VPN or third-party network filter, temporarily disconnect or pause it, reconnect the iPhone, and check Device Hub again. Re-enable it after the test.
Xcode uses network communication even over USB, so a working Finder/Configurator connection doesn’t rule out interference with the development connection. Apple explains this in TN3158: Resolving Xcode 15 device connection issues.
3. Try explicitly starting wireless pairing.
Since your iPhone is running iOS 27, put the Mac and iPhone on the same Wi-Fi network, then choose Device Hub > + > Pair Nearby Device…. Allow device discovery if macOS prompts, and follow the pairing instructions.
This is covered in Apple’s Device Hub guide.
Could you share the version/path outputs from step 1, whether any VPN or network filtering is installed, and whether the iPhone appears in the nearby-device pairing dialog? If an error appears there, its exact wording would help narrow this down.