it seems i have attached to the unity, but the break point still has no response; i have try to reintall my rider and unity, but i just doesn鈥榯 help
console msg: Input/Output redirection disabled: Debugger is attached to an already running process
but debug output windows output nothing
Please attach zip and attach logs from Help->Show log in Files.
it's my rider log zip, and two screenshot when i try to attach to unity process, thank you!
@Zhuangdum This should be fixed in Rider 2017.2.1. Could you please check whether the fix worked for you?
Closing due to inactivity. Please reopen if it hasn't solved the issue.
Still Have this on 2017.3
Same probleme, anyone have found a solution ?
2017.3.1.: having the same issue.
Input/Output redirection disabled: Debugger is attached to an already running process
"C:\Program Files\JetBrains\JetBrains Rider 2017.3\bin\runnerw.exe" "C:\Program Files\JetBrains\JetBrains Rider 2017.3\lib\ReSharperHost\JetBrains.Debugger.Worker.exe" 50585
Please post all logs from Help->Show log in Files, including "Debugger Worker" folder. Just everything except "threadDumps*". Also please mention do you have mono 2 or mono 4x mode in Unity.
@van800
log.zip
Mono runtime version: 2.0.50727.1433
@MohsenneChaverdie Hi! Could you please provide me with more details? What is your working scenario? According to logs your breakpoint is bound to correct location right after assembly load
I tested it again, and now mysteriously it is breaking at the break point correctly. The time that I tested it, Rider was not reacting to the breakpoint at all. Next time that happens, I will record a video of it. Thanks for such a good support.
@ThatFatPat @mvedie does it still reproduce for you in Rider 2017.3.1?
Closed due to inactivity, I guess fixed in Rider 2018.1
I'm also seeing this issue in 2018.1.1, attached clean log from an empty project with 1 script and a couple of breakpoints added here:
https://gist.github.com/atlemael/3634aa37b8dee0e0c9a477be324b2bf6
@atlemael Debug related logs are in "Debugger Worker" folder, please attach it.
I was getting the same error in 2018.1.1 using a recent trunk version of Unity. Switching to 2018.1.2 I get a more verbose error:

Here are my logs:
2018.1.2 Logs.zip
From times to times I have the same error as @danielbrauer
I've been able to "fix" it by disabling Rider plugin, settings Visual Studio as the editor, relaunching everything, letting Unity generate the unmodified projects for VS, attach the debug once.
Then back to Rider as the default editor, re-enable plugin and relaunch everything and breakpoints start to work.
I have the same error and I can't fix it. I'm now using VSCode instead.

@hugoBourretDesmarais Please attach DebuggerWorker logs of last unsuccessful run here
Where is this located?
https://rider-support.jetbrains.com/hc/en-us/articles/360001079770-How-to-collect-Rider-logs-
^ In logs folder there will a DebuggerWorker folder, that's the logs that we need to diagnose this issue
Here's the DebuggerWorker log file :
mono-sgen_2018-07-31__12-14-24.log
@hugoBourretDesmarais Is it possible to provide us with sample solution?
I had the same problem. Close all unity projects and restart solved my problem.
Having the same problem, can't fix it with any solutions above.
Log:
JetBrains.Debugger.Worker_2018-08-20__01-16-23.log
Sample project:
Debugger Sample Project.zip
Reproduction process:
@ryo0ka Have you tried Rider 2018.2 RC/Nightly builds? Your setup is Unity 2018.2 on Windows, right? What is your Runtime in UnityEditor?
@ryo0ka Debugging of the provided solution with Rider 2018.2 worked for me, but I was to attach Test script to Camera object and enter Play mode in Unity Editor.
What I did:
Had it work. Entering playing mode in Unity Editor (or from Rider) did start the debugger.
I was being confused by the "Debugger is attached to an already running process". The error actually doesn't do anything. Thank you for clarifying the process for me :)
I'm also having this issue, started right after updating to 2018.2.
None of the solutions above seems to work for me. Here are my logs:
2018.2_macos.zip
@hodor Does it reproduce on any project or just yours? What are your steps? Thanks!
@van800 I just tried on another project and got the same issue:
Input/Output redirection disabled: Debugger is attached to an already running process
"/Applications/Rider 2018.2.app/Contents/lib/ReSharperHost/runtime.sh" "/Applications/Rider 2018.2.app/Contents/lib/ReSharperHost/JetBrains.Debugger.Worker.exe" --mode=client --frontend-port=59152
Opened the project and created a new cs file in the assets folder.
Double clicked the .cs file to open the source on Rider.
Attached Rider to Unity Editor by clicking on the debug icon
I tried adding a breakpoint anywhere in the code and got the same problem.
@hodor It's normal output for debugger console tab. Have you attached your script to some game object?
@ArsenyChernyaev I'm working mostly on Editor scripts now. Besides that output, all my breakpoints are replaced by a grey stop icon with the error: Not found loaded method for (...)
Have you tried anything like the following
[InitializeOnLoad]
public static class PluginEntryPoint
{
static PluginEntryPoint()
{
Debug.Log("something");
}}
Yes, on the project I was working on sometimes it does work even though the breakpoints are all disabled and showing errors. But sometimes it also takes a long time for the code to break. Other times the breakpoint merely is disabled, and it the execution never stops.
I'll try on a new project and will let you know.
On a brand new project, the breakpoints are still greyed out by default and always with the same error.
I setup Editor and Runtime breakpoints. After running the project, the execution started to break with no delay on the right line.
I closed Rider and reopened my original project trough Unity. At first, the breakpoints were still disabled, but it started to break at the right time.
Everything seems to work now, even on my problematic project but I have no idea what actually fixed the problem :)
Still an issue on Mojave.
JetBrains Rider 2018.3.1
Build #RD-183.5253.26, built on December 26, 2018
JRE: 1.8.0_152-release-1343-b26 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.2
I've tried the solutions provided above and it still isn't connecting.
NOTE: Started working again after a second time deleting SLN & CSPROJ files in project, shutdown of mac, restart.
If it helps, I was initially trying to breakpoint in editor-mode code (driven by a selecting a menu option). This last time I successfully hit a breakpoint in play-mode, then hit stop, then again tested a breakpoint in editor-mode.
Had the same issue and fixed it. In my case problem appeared when I start project from mounted drive (via subst). Solved by starting project by full path (via Unity Hub) and cleaning csproj/sln files and obj, Temp, Library\ScriptAssemblies folders
Windows 10, Unity 2018.2.13f1, Rider 2018.3.1
I was getting this issue with skipping breakpoints in my Unity project with Untiy 2018.3.0f2 and Rider 2018.2. Rider and the project were installed on different hard drives.
Updated to Rider 2018.3 today, tried it on different hard drives, just like in the previous setup. The issue was not fixed, but I started getting grayed out breakpoints when I attach the debugger and warnings of type "Not found loaded method for" (as posted above by @danielbrauer for example)
Tried re-installing Rider on the same hard drive where the project is. Still getting the same warnings and breakpoints not triggering. Deleting the csproj/sln files and obj, Temp, Library\ScriptAssemblies folders did not help. Installed Unity Hub. Not sure if I understand what is meant by "starting project by full path", but just opening the project from Unity Hub did not change anything.
Would appreciate any help with this.

Same problem. 2 things have changed in my project around the time this started happening:
On reverting the project to a state before these changes, the breakpoints will work correctly.
@anthrich symlink reportedly brakes debugging.
Strange - after the revert, the symlink is still in place but debugging is working again. I'll see if I can pin it down any further.
Dear Devs! In case issue fires again, please create an issue in https://youtrack.jetbrains.com/issues/RIDER
and follow up here with a link.
Debugging is Rider core functionality and related issued have to be processed and planned in YT.
Thank you!
Still having this issue with Unity 2018.3.6f1, Rider 2018.3.3.
Will not attach to any breakpoints in my project. I first got the issue on Unity 2019.2 alpha, and downgraded to 2019.1 beta, thinking the alpha just wasn't supported. Still got the issue, so downgraded again to my current preferred version 2018.3.6f1, and still getting the issue.
I've deleted the Library, obj, all .sln / .csproj files in my project each time while downgrading, to no avail.
I'm also sure I'm using the most recent version of the plugin (at least, Rider tells me so).
Edit:
Here's my logs in advance.
log.zip
Edit2:
Resolved my own issue (doesn't appear to be the same bug). Info on my comment on youtrack https://youtrack.jetbrains.com/issue/RSPL-6957
This is still happening.
@doctorpangloss Issues with debugger are out of this plugin scope, please report then in https://youtrack.jetbrains.com/issues/RIDER. Thank you!
Most helpful comment
This is still happening.