"Cannot Resolve Symbol" - Rider, Windows, Resolve symbols between Editor and Runtime Assemblies

So, I opened my pet Unity project on my Windows box and because I've been using Rider at work on my Mac, I thought I would give it a go in Windows. However, I can't figure out why Rider can't resolve symbols.

Unity 2019.3 / Rider 2019.3

I imagine it must be the compiler configuration but none of the suggestions that I come across on the net thus far works. I open my project on my Mac and Rider resolves all the symbols just fine. The Unity project itself compiles and runs just fine in both Mac and Windows. It's definitely a rider config problem. i just have no idea what.

 

Thank you for replying. Unfortunately this was among the first things that I tried. I’m aware of how unity generates The solution and project files.

 

Rider works for my project on my mac... but not on windows. Rider works in Windows with the Tutorial projects... I feel like I might have to rebuild my project from individual source files.

 

I'm having a similar issue and both suggestions did not work unfortunately.
Also checked Settings -> Toolset and Build settings within Resharper but everything seems to be okay.

It's weird because packages like TextMeshPro are giving me problems as well. For example using TMPro is flagged as red and it says "Cannot resolve symbol TMPro".

I'm having a lot of errors in solution in rider but Unity compiles fine and I can run in editor with no problem. Any help is greatly appreciated!

 

Hmm. I have the same problem with another asset. Is deleting the library the only way to rebuild them? Can't you do it for a specific asset?

 

I might have fixed it! I went to the solution view, right clicked the asset and chose clean and rebuild, or something like that. The errors went away for now, but it's processing something now, so not sure if it will come back..

 

I get the same problem in Rider. Always with TextMeshProUGUI and TMP. Rider's analysis complains "Cannot resolve symbol 'TMPro'" and similar for TextMeshProUGUI. But there is no error in Unity. Every time, I end up doing some combination of the following and it normally goes away:

1. Rider > Disable Solution Wide Analysis, Close Rider, Open Rider, Rider > Enable Solution Wide Analysis.
2. Rider > Clean Solution, Rider > Build Solution
3. Rider > Open some scripts not currently open where there reference to TextMeshProUGUI or import TMPro

Not sure which of these steps fixes it, and not sure why this happens. Really annoying.

 

Hello,

I'm having the same issues with 2d lights. I guess it makes kinda sense because it's still experimental in Unity 2020 but there has to be a way for Rider to still detect it?

 

I'm currently using Rider 2020.3.4
Wanted to mention that a lot of the errors on my side happened when I upgraded the Unity packages for JetBrains Rider to 3.0.7.
Reverting back to 3.0.6 (or forcing it on the packages.json of Unity) will get rid of the errors.

Didn't try to do Clean solution like @ColdPixel suggested though.

 

• Close Unity and Unity Hub;
• Delete all the project (.csproj) and solution (.sln) files;
• Open your Unity project;

Solved the issue for me (for now). This is the second time in 2 days this has happened.

How do you upgrade / revert the Unity Packages that Rider uses, I couldn't find those settings within Rider anywhere?

 

That's on the Unity Packages Manager itself, you would have to go to the manifest and packages.json and force a number there.
But fyi, on a recently new project that I started I have updated to Unity 2021.1.14f1 and latest Rider version and it's working fine:

 

Thanks you for this. I was running into same problem when I tried to pull my project from git.

 

↑ This also worked for me, thanks

 

I've tried the various suggestions and it still fails for me. (Rider 2022.1.2/ Unity Editor 2021.3.5f1 LTS [Silicon]/ TextMeshPro Package 3.0.60 ) I have had other namespaces unresolved on other projects.

 

I have teh same issue as lemapp, with the exact configurations. For me, basic symbols like void or float are red and "Cannot resolve". I've tried all of the solutions posted above without success.

Note: I've just upgraded from 2020.3.11f1 to 2021.3.5f1 and only now encounter this error

 

Hello. I have not Rider, but VS2019 with Resharper and I had the same issue ("Cannot resolve symbol 'color' " in TextMeshPro)
In my case the following steps solved problem:
1) Close Visual Studio;
2) In Unity: Edit -> Preferences -> External Tools -> Regenerate project files
3) Open Visual Studio.
It may be obvious advice, but maybe it'll help someone

 

Same issue here. I tried all the cache clearing measures mentioned in the comments above but still experiencing the issue.

Rider: 2022.2.3, Unity: 2021.3.5f209

One thing that may be relevant: the package in question (NaughtyAttributes) that can't be referenced seems to be the only one that is displayed differently in the project folder view (with a git symbol):


I also integrate it into the project through the Package Manager, but maybe this can be a lead.

 

It works! Thank you! Solved my problems

 

If solution above doesn't work, try this:

https://rider-support.jetbrains.com...dows-Unity-Resolve-symbols-between-Assemblies

 

I had tried this solutions, but it still not work.

 

Had a similar issue today with cannot resolve symbol.... did above and reinstalled the hub followed by an uninstall and reinstall of the rider package, followed the advice by Rider on :
https://rider-support.jetbrains.com...dows-Unity-Resolve-symbols-between-Assemblies
Specifically the post by Sofia Byzova April 16th ending in :Invalidate and Restart

I still got all the errors but this time if you wait for it to find all the lack of symbols errors (on a big project) it finally cleans up and life returns to normal

 

^Sofia's post fixed mine