Can't Attach Visual Studio to iOS device

Hello everyone,
I've got a problem with iOS managed debugging in VS Community for Mac.
I'm using Unity 2018.2.6f1 and Visual Studio Community for Mac 7.4.3 (build 10).
I've checked all the settings for building my app and debugging, i can build without any problems and on startup the application on the iPhone shows a pop up saying: "Debug - You can attach a managed debugger now if you want".

But on the VS side, I can't select anything except "Unity Editor" as debug target.
I could not find a way to attach another target.
Does someone have any tips?
Thank you.

 

Wow, thanks!
You're a life saver, i didn't know that setting was there.
I would have never got it without your help.
Thanks alot!

 

I could attach the debugger, but it doesn't break on breakpoints.
macOS, Unity 2019.2.18
iOS 12, iPhone 5

 

A Unity script. Not a pre-compiled assembly.

 

@JoshPeterson As a quick aside, for us connecting VSCode to the editor or to an iOS device has been a no go for years - the debuggers don't connect, or they connect and disconnect immediately, or they beachball, or if they do magically connect they either don't break, or if they break they don't step in or step out correctly. I've filed bugs in the past but nothing seems to come of it. Prior to that, old MonoDevelop connecting to old Unity was an instant beachball on Mac as well, so Debug.Log has been my trusty friend for about 10 years.

I haven't checked the latest Unity so I'd be pleasantly surprised if it's working, but the last time I checked an iOS debug connection to an IL2CPP project it instantly failed (yes, the phone cellular was turned off, etc). In addition, the VSCode v1.1.4 verified package is currently broken on Mac (bug reported). I don't know how your devs using Macs don't hit the same problems everyone else seems to hit. I think the VSCode stuff is technically unsupported by Unity so fair enough it might break a bit, but as a verified package it breaks in a fresh project.

 

hi Josh, yep that's right, the VSCode debugger extension says it's unsupported in the extension description / docs which is a shame because VSCode as a C# and general purpose editor is great. I've not used Rider but always heard good things (tested their pre-release version for a few weeks but not tried it since). I'll reinstall Visual Studio Code for Mac and test an iOS connection/debug in 2019.2 sometime.

No doubt it's hard trying to keep all these tools working and improving as the .Net flavours and IL2CPP change under the hood. Thanks for your hard work and for being active in the forums too. Looking forward to seeing if and when all the new C#/.Net stuff makes it over the Unity fence.

 

I am attempting to debug a Unity (2018.4) project running on an up-to-date iPad from the latest Mac Visual Studio. I am able to see, from the Mac, the iPad open port that the Xcode debugger reports (Multi-casting "[IP] 192.168.1.9 [Port] 55000 ...snip...) but when I start debugging and try to attach to the process I see only Unity Editor in the attachment options in VS.

My build settings are:


The profiler pops up but nothing ever appears in it even when I turn off script debugging.

Any ideas on how to get beyond these blocker would be greatly appreciated.

I am able to attach to an Android device running the same Unity source, though.

 

@JackGrayBrain
You have to check 'Symlink Unity Libraries'. Please check my blog post.

 

Exact same issue, it’s says "This request is not supported by the protocol version implemented by the debuggee” when the break point hits... when is this going to be fixed?

 

Like JackGrayBrain I'm not seeing my IPad in the Mac Visual Studio dropdown:



My Unity build settings:



My Unity version is: 2019.2.21f1

My Visual Studio Version is: 8.6 (build 4520)

When I select "Build and run" from Unity and have my IPad plugged in the app launches and the profiler connects.

I've tried unplugging the usb cable and the airplane mode wifi trick.

Any ideas?

 

Looks like I was missing a key step. From Visual Studio instead of the dropdown I was using (pic in previous comment) I needed to:

Run > Attach to Process > Select my IPad

Works like a charm. My IPad is not plugged in to my Mac.

 

Hello i am also facing the same issue, cannot see my ios device in the attach the process. What can be the issue?

Felixmann can you please guide me how to resolve this issue.

 

Unity docs say that need to disable firewall on router, but it doesn't help.

 

I still wonder why do I have to put my iPhone into airplane mode to debug it?!? Every time I forget about this and I cannot debug it (I do not do Unity3D as full time). This is a unity thing that is super annoying. Xamarin VS, xCode doesn't need this. Any plan on removing this particular needs one day?

 

Hello! I am also facing into same issue after upgrading iOS to 16.1. Everything was working fine before iOS upgrade to 16.1 version on both iPad Pro and iPhone XS max. On old iPad Air 1 with iOS 12 script debugging works well. Exactly problem is in iOS 16.1, maybe security things that actually prevent the managed debugger from working.
I used latest Unity 2022.1.21f1 on Mac OS Ventura (13.0)
Please, if anyone faced how to solve this problem on iOS 16, let me know.
Thanks in advance!

 

I have the same issue. iPad with now iOS 16.1.1 is not detected by Visual Studio, but has also not been detected with iOS 16.0
The iPhone with iOS 14.4 is detected.
I also posted that problem on stackoverflow: https://stackoverflow.com/q/74728292/6796677

Can you please add a link to the Bug-Page as soon as the bug report has been created?

 

@JoshPeterson I too seem to be having issues trying to attach my iPhone 13 to my M1 max. I have checked all the checkboxes for debugging but the iPhone does not show up in the Attach to Process debugger. I can debug unity fine in play mode but as reported by @vasildx and @cgaisc with the latest versions of MacOS and IOs the i device does not show up plugged in to the computer or not.

Also when I was accessing camera's via web browsers (for barcode scanning), android and windows tablets and phones would have descriptive indicators returned when querying for camera. iPhones and iPads returned non descriptive hashes but would always return them in the same order. Using this allowed me to query the system and enumerate camera's by OS. It would seem as though when querying for network interfaces in IOS the same hold's true. I guess it is somewhat compounded by the fact that on IOS not all devices have cellular and I believe bluetooth would also show up as a network interface which means you really may have no idea. I would assume the first returned interface would be Wifi by default but if you have to turn off your cell radio I guess not.

 

We are having the same issue with our Mac mini M1 2020 on Ventura 13.1 with Unity 2021.3.17f1 and Visual Studio for Mac 17.4.4. We can't attach to our iPhone X with iOS 16.2 and our 5th generation iPad running iPadOS 16.3.

Airplane mode and Wi-Fi are both enabled.

 

Can confirm that this isn't working with iOS 16.3.1 (iphone 14 pro), Visual Studio for Mac 17.5 (build 1802), Unity 2021.3.10f1. iPhone 14 doesn't show up for Attach To Process.

When I opened the game in TestFlight on an old iphone 6s running iOS14.4.2 then the phone was found when selecting Attach To Process.

Has a bug been opened for this yet? If not, I can add one.

 

We can attach it, but once it hits a break point it breaks, this is a known issue for more than 1 year.

https://forum.unity.com/threads/since-unity-2021-debug-breaks-on-device-on-mac-il2cpp-build.1383372/

https://youtrack.jetbrains.com/issu...aks-and-game-freezes-for-IL2CPP-on-iOS-device

It happens since Unity 2021, both on Rider and VS

 

Same issue here. I can connect with Unity profiler and with Rider but not with Visual Studio 2022 Mac. I have tried using the IP I can enter it in the Attach to process window as Attach to but then the OK button disables as if the Attach to field works on only as a filter/search for the list of attachable processes.

 

Due to the issue in Rider ( https://github.com/JetBrains/resharper-unity/issues/2304 ), we've also been testing Visual Studio for Mac for debugging, and also had the same problems manually connecting. Turns out that Visual Studio for Mac doesn't really care where the broadcast message comes from, so it seems like sending UDPs from the dev machine allows Visual Studio for Mac to connect and debug (this could be done from Unity on the iPhone in C# as well). Stepping and variable inspection works as one would expect.

This workaround python script works on my setup (device is running iOS 16.3.1):
https://gist.github.com/trond-agens/3961db548f74d1e05153a2041d92fa98 (EDIT: You must adjust the IP ranges to match your local network and device)

 

I'm having the same problem, and can't figure out where to manually enter in the IP in VS Mac. When I go to Run > Attach Process, it only lists what it's detected. Where am I manually entering in the IP? Thanks.

 

Thanks @JoshPeterson, this saved my skin lol.

 

@JoshPeterson I tried this workaround but I still don't see my IP when I go to Attach to Processs. This is VS 2022 for Mac. Were you able to make it work?

I'm really glad you found out the cause of this issue! I'm looking forward to having the fix in Unity.

 

This is fantastic! Works perfectly.