MAUI iOS "The selected device was disconnected and cannot be accessed anymore from this machine"

All of a sudden I can't run any iOS apps on either simulators or physical devices.

It shows the name of the simulator I was using with a yellow triangle and the message "The selected device was disconnected and cannot be accessed anymore from this machine"

I'm using Rider 2023.3.3 and xcode 15.2.

Xcode is working, there's no pending updates, I can run swift apps from xcode without any issue. I can also run apps from Visual Studio for Mac. It's just Rider that is broken.

1
21 comments

I would like to know about this as well.  I have the exact same issue.  It just started giving me this error today.  I am on a Mac Mini M1 connected up to an older iPhone running iOS 17.latest ver.  I can't verify any other dev tools.

1

Just tried the same thing on VSMac and could see the device as well.

0

I see the exact same thing. In fact, I've seen all kinds of craziness, and that's been been the case ever since I started experimenting with MAUI in Rider. Is anyone _actually_ relying on Rider for professional MAUI development?

0

I've started using Rider just for MAUI on a trial, as vs4mac is end of life and I've found using full VS in parallels for ios development a bit clunky.

I don't think I'm going to be paying for Rider though, it's so unreliable.

1

Jessica Shannon Yes, I'm paying for it and Rider beats VS in almost any comparison. Just not for MAUI as far as I've seen. Way too much “Voodoo” happening

0

Jessica Shannon just as an fyi, i have found the vs to windows remote debugging to be very brittle.  I tried to setup vscode with the Maui extension and it was horrible.  Rider does give me actionable error messages whereas vscode just looked at me.  I spoke to someone on the Maui team, and to be honest, I never got the feeling that hey cared about the state of their dev tools for Maui.  Now, that could be for a number of reasons unknown to me.  Whatever, I’m a customer and I’m trying to do development on iOS and Android.  All of this used to be much better when it was xamarin not maui, which is a crack on msft, not JetBrains.  I hope something can be communicated about this issue in the next 24-48 hours.

0

Wallace B Mcclure yes it's quite worrying when the best tool for iOS MAUI dev is still VSMac and it's about to be axed. It feels like MAUI won't be around for much longer.

0

As an fyi, I created a basic project in vsmac with .net 7.  I got errors (mostly due to me), but eventually was able to upload to my phone.  I opened the same project in rider, and was unable to get my phone to be recognized.  Sad, but I feel that Maui is the problem.

0

Any new news on this?

0

Hello folks! 

Sorry for taking some time to respond. 

Could you please do the following: 

  1. Try the EAP version and let me know if the issue persists;
  2. Could you please try to clear the caches via File | Invalidate caches => Invalidate and restart and remove the .idea folder (find it in the Help > Diagnostic Tools > Special Files and Folders > PROJEct StorePath).
  3. Does it work in the Xcode itself? Are emulators there opened? 
  4. Could you please check the Xcode > Settings > Locations > Command Line Tools? Is it the same with Settings | Build, Execution, Deployment | Apple Platforms?

Responses you may post either here or to the aforementioned issue

Thank you in advance! 

 

1

Anna Morozyuk 

  • Clear the caches.  Did not do anything for me.
  • Work in xcode?  Sure, i see the device.  No error around the device.  I get a compile error in xcode, but that is a different discussion.
  • The two settings for my xcode command line tools seem to match up for me.
  • Trying the eap does tell me that my publishing profile is missing.  Oy vey.  I think I have all of my certs, devices, and profiles setup in my apple dev account.  They all look about right to me. <confused />
0

Rolling back to XCode 15.1 seems to have solved the problem for me.  I also noticed that there is an update for rider to 2033.3.4.  How do I keep up with what versions of xcode are supported?

0

Rider should support the current Xcode version. Thus, the issue seems like a malfunction, which we'd like to investigate further.  

 Trying the eap does tell me that my publishing profile is missing.  Oy vey.  I think I have all of my certs, devices, and profiles setup in my apple dev account.  They all look about right to me. <confused />

Could you please do the following: 

  1.  Open solution in Rider EAP with the 15.2 Xcode;
  2. Open Xcode from Rider by right-clicking the project in the solution explorer and choosing Open in Xcode option;
  3. Re-generate iOS provisioning files;
  4. Try to build the app again and check for the device list. 

Is it working for you? if not, can you please record a screen-cast of the issue and attach it in the YouTrack comments

I cannot reproduce this issue nor on intel, neither on arm machine with the 15.2 version of Xcode and both current Rider EAP and 2023.3.4 versions.  Thus, I'd like to verify if it persists in the EAP version on your side. 

Thank you in advance for your cooperation!

 

 

 

0

XCode 15.3 is the most recent version.  I have set everything to 15.3, and I get the same error as has been posted about.  I am using an arm m1 mac mini with Mac OS 14.3.1.

0

I futzed around with things, went back to xcode 15.1 and eventually got everything to work again.  I don't have any data beyond the pictures that Jessica posted.

0

The same issue!

Was ver. 2023.3. Then, I installed 2024.1 EAP 7 and there it worked. Then, I updated later to EAP 9 and it stopped to work in the EAP, BUT started to work in  the 2023.3…

I updated the Xcode to the latest today and the same result… Mystics…

Please, fix it ASAP, as it is a vital too for MAUI development.

0

Anna Morozyuk  File | Invalidate caches => Invalidate and restart  solved the problem! Thank you!!!

0

Hello Gorkin ,

Glad you could find a workaround.

Wallace B Mcclure , Jessica Shannon , Jonas Rembratt , could you please try thew same?

0

I no longer have this issue. I do, however, invalidate caches/restart regularly as Rider often struggles to keep up with refactoring passes (and I refactor pretty aggressively each week) so it might be that's what solved it.

0

Please sign in to leave a comment.