Errors in solution that do not really exist


For some reason, Rider goofed and keeps saying I have tons of errors in nearly every file, but when I open a file it realizes that there are no errors there and all the mentions and indicators of errors for that file go away, but that only happens if I actually open the file and give it a second to upadate.

Is there a way I can force the whole project to properly update? I tried to right-click on a folder and selected Inspect Code, then selected Whole Solution and it brought up a window and then scanned all files but they all came back with the same false errors and would go away and leave the list once I actually opened the file, but I don't want to have to go through and open every single file in a large Unity project with a lot of, not only my own code, but code from third party assets.


JetBrains Rider 2020.1.3
Build #RD-201.7846.1, built on May 15, 2020
Runtime version: 11.0.7+10-b765.53 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
.NET Framework 4.0.30319.42000
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 2900M
Cores: 32
Registry:, ide.tree.horizontal.default.autoscrolling=false,, ide.tooltip.showAllSeverities=true,, ide.borderless.title.product=false, ide.title.debug=true,,, ide.tooltip.initialDelay.highlighter=0, search.everywhere.settings=true,,,, ide.borderless.title.debug=true, ide.borderless.title.project.path=false, localHistory.daysToKeep=30, search.everywhere.pattern.checking=false, ide.tooltip.initialDelay=0, ide.borderless.title.classpath=false, ide.balloon.shadow.size=0, ide.require.transaction.for.model.changes=false
Non-Bundled Plugins: String Manipulation, org.intellij.plugins.markdown, com.chrisrm.idea.MaterialThemeUI, com.daylerees.rainglow, com.intellij.resharper.HeapAllocationsViewer, com.sburlyaev.terminal.plugin, com.wakatime.intellij.plugin, net.vektah.codeglance,, izhangzhihao.rainbow.brackets

Comment actions Permalink


Please try `File -> Invalidate caches/Restart`. Does it help?

Comment actions Permalink

Yes, that is what I ended up having to do, but I was just hoping that there might be a less extreme method to rescan the solution or similar. It does not sound like there is, though.

Comment actions Permalink

I'm afraid there is no other solution. It looks like your caches was corrupted, that is why Rider's analyser got confused. By the way, please let us know if you find steps to reproduce the issue. We'd be happy to fix it.


Please sign in to leave a comment.