Unable to connect Debugger to Unity Player Follow
I have no problems debugging with the debugger attached to the Unity Editor, but I have recently run into an issue that appears to only happen in my builds.I am completely unable to connect to a running player.
When I use "Run->Attach to Unity Process..." The only process listed is the Editor, and not the player.
What am I misunderstanding?
Please sign in to leave a comment.
Experiencing the same. Unity 2019.2.2f1 and Rider 2019.2.2 x64
Could you please specify what OS are you using? Please make sure you have no pending updates or reboot, as we have encountered similar cases where it seems to be causing the issue. If the issue persists, then I would appreciate you collecting the logs with Trace scenario for Debug(Help | Enable Trace scenario | Debug), reproducing the issue and Help | Compress logs for further investigation. Please attach the logs here or create a new issue on YT: https://youtrack.jetbrains.com/newIssue and attach logs to it. Thank you in advance!
Windows 10. No pending updates or reboot.
Thank you for keeping me posted. As mentioned previously, we will need to investigate the diagnostics information for further suggestions. Please use the instruction above for collecting the logs. Thank you in advance!
Having exactly the same problem - just recently upgraded to 2019.2.3 - previously it was working just fine (2019.1.?)
We have discovered an issue with attaching to Unity Player: RIDER-34039, the fix for it will be added to the future version.
This bug has been hampering development now for over a month - I cannot debug my Unity OSX apps - I am forced to use visual studio - when will this be fixed? Will you issue an early patch? As an interim measure how can I revert to the earlier, working version of Rider?
As it is mentioned in the issue, fix is added to Rider 19.3 EAP 3, could you please clarify if you have tried the latest EAP and if the issue persists?
I am getting mad of this! This is so unreliable!!! This happens from time to time! If you try 10 times, 9 times will fail to find the Unity player on Android.
Rider version: 2020.1 (#RD-201.7846.1 built on May 15 2020).
P.S. It looks like everytime it doesn't show any Unity editor or player session, then you have to click 'manually add' and add something, then all shows up (including the session that should be found and the fake one you type). Otherwise it's keep rotating and show nothing! This is a obviously a bug.
Could you please enable Trace scenarios for Unity in Help | Diagnostic tools | Trace scenarios, reproduce the issue and collect full log bundle via Help | Compress logs? Please attach the log bundle with a new issue on our bug tracker. It will help us to take a closer look at the issue. Thanks in advance!
Same here, using Rider 2020.2.4. Tried with two different devices, connected via usb, ports set and adb connected, no luck. It doesn't work even if I add it as a custom player. Tried with 2020.3 EAP too, same story. I can't debug anything via Rider except Unity itself.
We'd be grateful if you collect Rider logs and create a new issue on Rider bug tracker as Olga Diakonova described in the previous message. Please use the latest 2020.3 EAP build for that.
Thank you in advance!