iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2

I am unable to use my iPhone 17 Pro as a run destination in Xcode. The device appears at a low level, but CoreDevice / devicectl keeps reporting it as unavailable.

Environment • Mac mini (Apple Silicon) • macOS 26.3 (Build 25D125) • iPhone 17 Pro • iOS 26.3 • Xcode 26.3 (Build 17C529) • Xcode 26.4 beta 2 (Build 17E5170d)

Symptoms • The iPhone appears in Finder • On the iPhone, I tapped “Trust This Computer” • Developer Mode is enabled • Apple ID is added in Xcode Accounts • Team is configured in Signing & Capabilities • iOS Platform Support is installed • The device still does not become available as a run destination • Devices and Simulators does not show it in a usable state • xcrun devicectl list devices still shows unavailable

Output of xcrun devicectl list devices

Failed to load provisioning paramter list due to error: Error Domain=com.apple.dt.CoreDeviceError Code=1002 "No provider was found." UserInfo={NSLocalizedDescription=No provider was found.}. devicectl manage create may support a reduced set of arguments. Name Hostname Identifier State Model


   CAC1B56A-C3B4-59FF-8F9D-659277C7C76C.coredevice.local   CAC1B56A-C3B4-59FF-8F9D-659277C7C76C   unavailable   iPhone18,1

What I already tried • Apple cable • Different USB/Thunderbolt ports • Direct connection to rear ports • Restarted both Mac and iPhone • Restarted Xcode • Ran sudo killall usbmuxd • Ran sudo pkill -9 remoted • Upgraded Xcode from 26.2 to 26.3, then to 26.4 beta 2 • Ran sudo xcode-select -s /Applications/Xcode-beta.app • Ran sudo xcodebuild -runFirstLaunch • Reset “Location & Privacy” on the iPhone, then trusted the Mac again • Still remains unavailable

Additional note

ioreg shows the iPhone, so the physical USB connection seems to exist. However, at the CoreDevice / devicectl layer the device remains unavailable, and Xcode cannot use it for on-device build/run.

Is this a known issue with macOS 26.3 / iOS 26.3 / Xcode 26.4 beta 2? Any workaround or additional debugging steps would be appreciated.

It would be helpful if we could get a bug report with attached logs from both Mac and iOS. Please see our instructions for capturing Core Device logging for both platforms and attach the collected logs to your report, and then post the FB number here.

— Ed Ford,  DTS Engineer

Thanks. I’ll collect the Core Device logs from both macOS and iOS, file a Feedback Assistant report with the attached logs, and post the FB number here once submitted.

I have ssen something similar on the last three beta releases. it tells me that IOS 26,4 is unavailable even though it is in the loaded list. I am running with an M3 iPad. I have two different FB reports in the last few days,

Thanks for sharing — that’s very helpful.

I’m seeing a similar “unavailable” state on my side as well, even though the device is detected at lower levels (Finder sees it, trust is established on the device, and Developer Mode is enabled). I’ve already updated my Feedback report with Core Device logs from both macOS and iOS.

This makes me think it may not be isolated to a single machine-specific setup.

Thanks, Ed.

My Feedback report number is:

FB22183081

@TE2026, thanks for filing that report. Would you mind also opening a code-level support request so that I can discuss the situation with your particular Mac directly with you? We found some useful insights in the logs you attached, but they're potentially really specific to you instead of being broadly useful to the community.

— Ed Ford,  DTS Engineer

Thanks, Ed. I tried the code-level support request link in your post, but it currently leads to a “The page you’re looking for can’t be found” page on my side.

I’m signed in to my Apple Developer account. Is there another direct link I should use to open the request?

I had a typo in my link, here is the right one: https://developer.apple.com/support/technical

— Ed Ford,  DTS Engineer

Thanks, Ed. I checked the code-level support request page and pushed Start Your Request, but my account currently can’t access it.

"Your account can’t access this page.

There may be certain requirements to view this content. If you’re a member of a developer program, make sure your Account Holder has agreed the latest license agreement."

It may be related to my current Apple Developer Program membership status, which I haven’t completed yet, but I’m not certain.

For now, I’ll continue through the existing Feedback report and the forums route, and I’ll follow up here if I receive any additional findings.

@TE2026, ok, thanks for letting me know about not having a developer account. Let me try to get some more info from you here, if you know.

What we are able to tell through your report is that there are system directories on your Mac that have a different owning file user than expected, where the directory is owned by uid 502 instead of the expected uid 501, and that's tripping up the device management infrastructure. This is pretty unusual, and it would be helpful to us to figure out how you got into this situation, if possible. Here are some questions to maybe help you think through things, but I'm really looking for anything that you can point out as potentially unusual in how this Mac is set up or used:

  • Have you migrated this macOS user account to different Macs over many OS versions?
  • Is there only one user account on the Mac, or is this Mac used in some sort of a multi-user environment?
  • Is this Mac managed in some way, such as by a company or educational institution, according to institutional IT policies? This includes if there's any Endpoint Security type software that's been installed now or in the past.
  • Have you ever needed to disable SIP on your Mac for any reason and then run commands in Terminal in that reduced security environment?

As I said, those are just meant to be some questions to get you thinking. If you aren't sure, that's ok, but please let me know either way.

— Ed Ford,  DTS Engineer

Q1: Yes, I used Migration Assistant to move files to this Mac mini (Apple Silicon). I believe I only migrated files, not the full user account. My previous Mac likely had uid 502 assigned to my user account, which may have carried over to the system directories on this new Mac. Q2: There is only one user account on this Mac. Q3: No, this is a personal Mac, not managed by any organization. No endpoint security software installed. Q4: I don’t believe so. This Mac mini is relatively new and I don’t recall ever disabling SIP. Please let me know if there’s any additional diagnostic information I can provide, or if there’s a recommended fix for the uid mismatch.

iPhone 17 Pro on iOS 26.3 stays unavailable in xcrun devicectl list devices even with Xcode 26.4 beta 2
 
 
Q