XCode update to handle iOS 15.3?

After updating my iPhone/iPad to 15.3 last night, I tried to Run an app from XCode (13.2.1) on my Mac, but I'm getting the Failed to start remote service "com.apple.debugserver" on device. error.

I can Run the app through the Simulator, so it's not life-or-death, but I find running the apps on the phone easier to 'play' with.

Anyone know if an XCode update is imminent to allow for testing on a device w/ the new iOS?

  • I need this too. Apple please respond quickly, we have product to build.

Add a Comment

Accepted Reply

Xcode 13.2.1 should work fine with iOS 15.3, after it downloads the necessary files from the device. Plug it in and check the Devices and Simulators window to make sure there’s no big yellow error message. Maybe reboot the Mac and device too.

  • I just restarted xcode 13.2.1, no change in ios deployment target drop-down, still only showing 15.2 as latest. Then powered off the ipad with 15.3Beta, powered off the mac, then power on both devices, start xcode, clean build folder, drop-down still shows 15.2 as latest, then build and same issue. Devices & Simulators status has no issues. Is there a way to re-trigger the download of necessary files from the device?

  • Not sure how this is the accepted answer, especially because Xcode 13.2.1, doesn't support iOS 15.3!!

  • Not sure what you mean by “support” there. The linked release note shows that Xcode 13.2.1 comes with iOS 15.2 SDK, but there’s no separate 15.3 SDK anyway. (The next Xcode beta has a 15.4 SDK.) And aside from the troubleshooting needed on some setups for whatever reason, using this Xcode with a 15.3 device does work.

Add a Comment

Replies

Xcode 13.2.1 should work fine with iOS 15.3, after it downloads the necessary files from the device. Plug it in and check the Devices and Simulators window to make sure there’s no big yellow error message. Maybe reboot the Mac and device too.

  • I just restarted xcode 13.2.1, no change in ios deployment target drop-down, still only showing 15.2 as latest. Then powered off the ipad with 15.3Beta, powered off the mac, then power on both devices, start xcode, clean build folder, drop-down still shows 15.2 as latest, then build and same issue. Devices & Simulators status has no issues. Is there a way to re-trigger the download of necessary files from the device?

  • Not sure how this is the accepted answer, especially because Xcode 13.2.1, doesn't support iOS 15.3!!

  • Not sure what you mean by “support” there. The linked release note shows that Xcode 13.2.1 comes with iOS 15.2 SDK, but there’s no separate 15.3 SDK anyway. (The next Xcode beta has a 15.4 SDK.) And aside from the troubleshooting needed on some setups for whatever reason, using this Xcode with a 15.3 device does work.

Add a Comment

I'm not sure what ended up working, maybe force restarting the iPhone (just shutting it off and then restarting it didn't work) is what ultimately did it. Along the way, I used the Devices and Simulators window to remove all the installed apps, unpair iPhone, re-pair iPhone, and uncheck Connect via Network, while also rebooting both Mac and iPhone.

When I originally checked the DandS window, the iPhone had a yellow warning, which I wish I'd copied down before restarting everything--something to do with icons, I think. My iPad had a red warning saying that it was locked and to reconnect it... even though it was connected. Did the same unpair/re-pair/etc. things with that as with the iPhone and eventually it worked as well.

I can't get xcode 13.2.1 to connect to ios 15.3, even after downloading the necessary xCode files and rebooting everything twice. Anyone have suggestions?

  • I'm in this exact category. 13.2.1 and cannot deploy and run an app on my now updated iphone to 15.3.

  • Same, after I got the new update the computer could no longer build my project on the device

  • update: I tried again, without any updates to my system or phone that I am aware of, and, it works now. Not sure why.

Add a Comment

I have the same problem

same problem here.

What's the status on this? App Review denies my app because it apparently crashes on 15.3, but I have no way of testing it on iOS 15.3?

Xcode 13.2.1 is, in general, able to work with iOS 15.3 devices. I just tested this here in my office:

  1. Using Xcode 13.2.1 on macOS 12.2, I created a dummy test app with this code:

    override func viewDidLoad() {
        super.viewDidLoad()
        print("Greetings from \(UIDevice.current.systemVersion)")
    }
    
  2. I ran it on my device and it printed:

    Greetings from 15.3
    

I have no way of testing it on iOS 15.3?

Issues like this crop up regularly. Indeed, this post has my recommendations from the last time I saw folks hitting this issue.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Add a Comment

Thanks restarting the phone fixed this issue for me.

killerSwitch wrote:

seeing that Xcode 13.2.1, doesn't support iOS 15.3

The doc you referenced says:

Xcode 13.2.1 includes SDKs for iOS 15.2

That’s not the same as saying it doesn’t support iOS 15.3, because there’s a difference between SDK support and device support. For minor iOS updates it’s common for a previous version of Xcode to support a newer version of iOS.

In this situation it’s better to look at the iOS release notes, and here the iOS & iPadOS 15.3 Release Notes point you at Xcode 13.2.1.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

  • That doesn't really help. Xcode constantly struggles with point updates. Even if there is device support for newer iOS versions. I never ever experienced a seamless minor update to the latest iOS version if Xcode does not have the proper files. Only patch updates do not seem to cause trouble. If i see Apple pushes out a new iOS version without an accompanying Xcode update i don't update my device as this just screams trouble.

Add a Comment

Xcode constantly struggles with point updates.

I have to say that’s not my experience, and I regularly exercise this case.

I do work hard to make sure that I only use supported configurations. Specifically:

  • I never install Apple internal stuff; I always stick with what we ship (or seed) to developers.

  • I don’t modify my Xcode install [1].

  • I don’t run Xcode under Rossetta.

  • I don’t mix my betas. If I’m working with an iOS beta, I have to use an Xcode beta, but I run that Xcode beta on a production macOS and target a ‘victim’ iOS device running the beta. Similarly, if I’m working with a macOS beta I install it, and its matching Xcode beta, on a victim Mac (a victim virtual Mac, if I can get away with it).

I’m not saying that there aren’t real problems out there. However, my experience is that, if we accidentally ship an Xcode with broken device support, we hear about it really quickly. It’s not the small trickle of reports I’m seeing on this thread, it’s a torrent.

Finally, the last time I waded into a thread like this I posted a sets of hints and tips for how to investigate such issues. I encourage you to:

  1. Resume installing dot releases (waiting a week or so after each release to let the early adopters flush out the problems :-).

  2. If you hit problems, run through those steps to try to isolate the cause.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] I regularly see folks recommend copying device support directories from one Xcode to another. That is unwise.