Cannot resolve symbol java intellij idea ошибка

This problem happens intermittently for different libraries and different projects.
When trying to import a library, the package will be recognized, but the class name can’t be resolved.

If on the import statement, I right-click -> Goto -> the package's declaration, I see all the decompiled classes displayed in the side pane — Including the ones I need —
If I try to auto-complete the import statement, I notice the class I need is not featured in the dropdown.

I tried invalidating caches already, doesn’t work. I cannot find any class conflicts — there is no other jar file in my classpath with the same package name.
I am able to import this class into other projects.

Please see screen shots:

Anyone have a clue?

File -> Invalidate Caches/Restart
And
Build your project

I faced a similar issue, Mike’s comment helped me move in the direction to solve it.
Though the required library was a part of the module in my project too, it needed a change of scope. In the module dependency, I changed the scope to «Compile» rather than «Test» and it works fine for me now.

Had the same problem till I noticed that the src folder was marked as root source instead of java!
Changing to only the java (src/main/java) to be the source root solved my problem

I found the following answer from @jossef-harush and @matt-leidholm useful from another link

• in IntelliJ editor, click on the red keyword (Integer for example) and press ALT + ENTER (or click the light bulb icon)
• select Setup JDK from the intentions menu

• click on Configure

• In my case, the JDK path was incorrect (pointed on /opt/jdk1.7.0_51 instead of /opt/jdk1.7.0_65)

• click on the ... and browse to the right JDK path

• let’s clear the cache

answered Oct 28, 2017 at 17:40

answered Sep 18, 2018 at 5:35

After a long search, I discovered that a dependency was somehow corrupted on my machine in a maven project. The strange thing was that the dependency was still working correctly in the compiled java code. When I cleaned and rebuilt my maven dependency cache however, the problem went away and IntelliJ recognized the package. You can do this by running:

mvn dependency:purge-local-repository

Intrestingly, the source of my problem hence wasn’t IntelliJ, but maven itself.

answered Feb 14, 2019 at 13:46

For 2020.1.4 Ultimate edition, I had to do the following

View -> Maven -> Generate Sources and Update Folders For all Projects

The issue for me was the libraries were not getting populated with
mvn -U clean install from the terminal.

answered Jul 25, 2020 at 2:29

Try cleaning maven from upstream by:

  mvn -U clean install

answered Jul 27, 2021 at 12:56

@Anton Dozortsev I was driven crazy by a similar behavior; I ended up re-installing the IDE a bunch of times, only getting past the issue after removing the IDEA app, all caches, preferences, etc.

I tried all kinds of steps in the interim, (like restarts, invalidations, deleting .idea and *.iml files, and others.)

Turns out, the problem was due to IntelliJ’s idea.max.intellisense.filesize setting. I had set it to 100KB, which was smaller than my dependency’s size, leading to IntelliJ showing it as unknown, just like in your screenshot.

Fix:

1. Click on Help -> Edit Custom Properties

2. Set the property to a larger value; the default is 2500KB
   idea.max.intellisense.filesize=2500

answered Jun 12, 2017 at 17:09

Please try File-> Synchronize. Then close and reopen IntelliJ before you invalidate.

Once I restarted. I would have invalidated but the synchronize cleared everything after restarting.

answered Jul 30, 2019 at 15:28

Simple Restart worked for me.

I would suggest first try with restart and then you may opt for invalidating the cache.

PS : Cleaning out the system caches will result in clearing the local history.

answered Dec 9, 2016 at 23:02

I found the source cause!

In my case, I add a jar file include some java source file, but I think the java source is bad, in Intellij Idea dependency library it add the source automatic, so in Editor the import is BAD， JUST remove the source code in «Project Structure» -> «Library», it works for me.

answered Apr 23, 2017 at 0:02

What did it for me is to edit the package file in the .idea folder as I accidentally added sources to this jar library and android couldn’t resolve it by deleting the sources line as marked in the b/m picture library error.

Then rebuild the gradle and bam problem solved.

I had the same issue and the reason for that was incorrect marking of the project’s sources.

I manually created the Root Content and didn’t notice that src/main/test folder was marked as Sources instead of Tests. So that is why my test classes were assumed to have all their test libraries (JUnit, Mockito, etc.) with the scope of Compile, not Test.

As soon as I marked src/main/test as Tests and rebuilt the module all errors were gone.

answered Jan 3, 2018 at 18:54

answered Oct 25, 2018 at 11:58

Nothing I tried above worked for me (not that I tried every suggestion). What finally did the trick was to rename the class — I just added a 2 to the class name and filename. Then I resolved all the references manually. (Since they weren’t recognized, the refactoring did not change the references automatically.)

Once the «2-version» was happily resolved everywhere, I was then able to refactor and remove the 2 from the class and file, and everything was then as it should be.

answered Dec 24, 2019 at 21:59

in my case the solution was to add the project as maven project, besides the fact that i imported as maven project 😛

go to pom.xml -> right click -> add as maven project

answered Jan 29, 2020 at 10:42

answered May 18, 2021 at 15:32

Also, check your class is not in compile exclusions

If you see, that there is a little grey cross in left top corner, you must remove class from compile exclusions

How to remove

answered May 26, 2021 at 13:29

Old question, ’21 response. I ran into the issue where my go build would build code successfully but my Goland IDE showed missing modules or dependencies. I tried Invalidating Caches and Restart, but had the same problem. From another S/O thread, I tried adding the GO111MODULE=on to my Path Variables, but that didn’t resolve the IDE problems either.

What worked for me was picking the correct GOROOT path in Preferences > Go > GOROOT.

I had two versions of go installed, one by brew and one from the online Go installer. I selected the brew install path, and my IDE was able to resolve the dependencies properly.

answered Oct 25, 2021 at 20:24

Faced similar issue,
I Updated Intellij and error start coming — Can’t Resolve Symbols.

Went to Plugins, Updated the plugins & Restart
Problem Solved !!

answered Apr 13, 2022 at 15:05