Intellij Cannot resolve symbol on import

Question

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?

Are you sure that the library was added to the module? It could be added as a project library but not be on the modules classpath. — mkobit, Nov 16 '14 at 00:02
yes -- In Project Structure, the library is added as a dependency -- Actually, I think this is a bug in Intellij -- Happens randomly for different libraries/projects -- Recreating the project from scratch usually fixes it — a5af, Nov 16 '14 at 15:23
If everything mentioned in the answer is proper. close the project and re import again. this solved this issue for me. — Hari Krishnan, Oct 16 '17 at 09:38
I tried invalidating caches and restarting, but the only thing that worked for me was wiping out the .idea directory completely, then creating a new project from scratch. — sheldonkreger, Aug 10 '16 at 00:07
In my case the problem was that I had not configured an SDK for the project - after I go to Project Structure and set the appropriate SDK it got resolved. — recepinanc, Dec 23 '21 at 15:56

score 489 · Answer 1 · edited Nov 08 '21 at 11:01

489

You can try invalidating the cache and restarting IntelliJ, in many cases it will help.

File -> Invalidate Caches/Restart

edited Nov 08 '21 at 11:01

Ivar

6,138
12
49
61

answered Dec 16 '14 at 16:01

sahitya

5,180
2
9
12

1

cleaning project also helped – GeRyCh Dec 14 '15 at 10:43
3

@GeRyCh IMHO, Eclipse cleaning = Intellij Invalidate cache – Gangnus Aug 05 '16 at 15:32
Didn't work for me too. My JUnit was a 'Global Library'. When I remove this and add IntelliJ's own JUnit5 distribution, it works. When I then convert this dependency to a global library again, the errors return. I suspect this is a bug because converting it to a project library instead works fine. – Mark Jeronimus May 08 '17 at 12:59
This removed the .iml file in my environment. Re-generating/Re-importing it resolved the issue though. – h0r53 Jun 18 '17 at 19:37
13

I have this problem at least once a day since a few weeks. Really stresses me out as re-indexing everything takes forever. – spyro Feb 15 '19 at 10:32
This worked for me after opening a project from Spring Initializer – Taimoor Ahmad Nov 18 '20 at 23:16
this worked for me, curious why is there such an issue from time to time? whats the cause of it? – Max Jul 29 '21 at 14:49
2

After "Invalidate Caches/Restart", you have to wait for re-index when you open any project! It's really annoying! I'd rathor delete that file and create it again, wtf! – Nano Aug 20 '21 at 04:16
‘Invalidate Caches/Restart’ closes all of my Java projects and the IDE will restart. So, if you’ve got more than two projects open, you might want to think twice before doing that. – johnnyasd12 Apr 19 '23 at 09:07

score 59 · Answer 2 · edited Feb 07 '20 at 15:53

59

There can be multiple reasons for this. In my case it was wrong source root issue. Invalidate caches didn't work along with other solutions.

Check your module source roots.

Project Structure (Ctrl+Alt+Shift+S).
Modules
Select your problem module.
Change tab on top of window "Sources".
Remove unwanted source roots. Keep one and add src and test source roots in this root.

edited Feb 07 '20 at 15:53

inetphantom

2,498
4
38
61

answered Oct 07 '15 at 17:54

Vipin Thomas

746
6
7

3

I do not know if this works for some people, but it seems so, and I wonder the reason why: actually your next Gradle sync will recreate all of those source directories you have just removed. – Fran Marzoa Apr 05 '18 at 16:36
1

It seems that when you have multiple source(src) folders issues arises. This is probably causes by a duplication of paths. In may case I had the main source folder and sub folder within source with additional packages. Ensure that there is only one source folder, and all your sub folder should not be added to source. This will ensure that there is no duplication of file paths. Thanks @inetphantom. – Vectoria Aug 13 '20 at 10:59
In my case, I had Groovy sources in different folders. I had to explicitly add them as as sources to remove "Cannot find symbol" errors on my imports. – sh87 Oct 16 '20 at 04:09
In my case, a target folder was excluded from the sources , this target folder has some files which are generated after compilation – ASharma7 Oct 18 '22 at 02:41

score 41 · Answer 3 · edited Sep 02 '20 at 20:33

41

File -> Invalidate Caches/Restart And Build your project

edited Sep 02 '20 at 20:33

TuGordoBello

4,350
9
52
78

answered Feb 13 '18 at 04:14

Harsh Mishra

1,975
12
15

score 36 · Answer 4 · edited Mar 23 '18 at 15:56

36

IntelliJ has issues in resolving the dependencies. Try the following:

Right click on pom.xml -> Maven -> Reimport
Again Right click on pom.xml -> Maven -> Generate sources and update folders

edited Mar 23 '18 at 15:56

Joern Boegeholz

533
1
8
25

answered Feb 02 '18 at 19:24

Chandlersingh

369
3
2

2

There is no "Reimport" after right-clicking -> Maven. There is reload. – JL_SO Dec 07 '21 at 08:34
Right click on pom.xml -> Run Maven -> Reimport – fiddle May 04 '22 at 12:59
Right click on pom.xml -> Maven -> Reload project worked for me..!! – Jaison Jun 06 '22 at 07:49

score 31 · Answer 5 · answered Sep 11 '19 at 16:12

31

Run this command in your project console:

mvn idea:idea

Done. Had this issue many times. Tried 'Invalidate Cache & Restart' and all other solutions. Running that command works perfect to me. I'm currently using IntelliJ 2019.2, but this also happened in previous versions and solution worked as well.

answered Sep 11 '19 at 16:12

Liuver Reynier Durán Pérez

365
3
4

1

Btw this maven plugin is no longer [maintained](https://maven.apache.org/plugins/maven-idea-plugin/) – nabster May 02 '20 at 20:08
3

What if we're using gradle ? – PAA Jun 17 '21 at 11:40
1

Some further info on the command is available here: https://maven.apache.org/plugins/maven-idea-plugin/usage.html – Bouramas Sep 03 '21 at 09:51

score 17 · Answer 6 · answered Jun 25 '18 at 13:20

17

File -> Invalidate Caches/Restart or rebuilding the project did not work wor me.

What worked for my Gradle project was to "Refresh all Gradle projects" from the Gradle tab on top-right corner of IntelliJ v2017, using the yellow marked button shown below:

answered Jun 25 '18 at 13:20

eaykin

3,713
1
37
33

1

This answer did the job for my Maven project also. For IntelliJ 2018.3.4 the icon stays the same (blue turning arrows) but the exact title of the option is called 'Reimport All Maven Projects'. Huge big up to the author, it is so relieving to find a correct solution for your problem after a one hour research – TomateFraiche Feb 07 '19 at 18:26
For me, it's a combination of invalidating caches, restarting, and then refreshing all Gradle projects. – Eric Ballard May 27 '23 at 18:45

score 13 · Answer 7 · edited Sep 03 '15 at 11:03

13

Check your module dependencies.

Project Structure (Ctrl+Alt+Shift+S).
Modules
Select your problem module.
Change tab on top of window "Dependencies".
Check what needed library (maybe, you need to add specified library in the tab 'libraries') or module has listed here and it has right scope ('complile' mostly).

edited Sep 03 '15 at 11:03

Jordi Castilla

26,609
8
70
109

answered Sep 03 '15 at 09:18

Artem Moiseyenko

139
1
5

score 11 · Answer 8 · answered Apr 30 '15 at 10:50

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.

score 6 · Answer 9 · answered Jul 11 '18 at 22:31

6

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

answered Jul 11 '18 at 22:31

Pipo

4,653
38
47

score 5 · Answer 10 · answered Oct 28 '17 at 17:40

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

IntelliJ intentions menu

click on Configure

Project SDK selection dialog

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

Broken Configure SDK dialog

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

Fixed Configure SDK dialog

let's clear the cache

IntelliJ File menu

score 4 · Accepted Answer · answered Feb 02 '23 at 04:54

I tried every answer here , What fixed my issue was deleting .idea folder , I did invalidate caches and restart before that and a simple restart after deleting .idea , The IDE asked to reimport gradle project , after the import everything started working normally.

score 3 · Answer 12 · answered Feb 14 '19 at 13:46

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.

score 2 · Answer 13 · answered Sep 18 '18 at 05:35

2

Right click on pom.xml file, go to Maven click on Reimport. I had similar problem and this worked for me.

answered Sep 18 '18 at 05:35

rdutta

103
1
5

user1599755 · Answer 14 · 2020-07-25T02:39:51.920

2

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.

edited Jul 25 '20 at 02:39

answered Jul 25 '20 at 02:29

user1599755

149
1
6

score 2 · Answer 15 · edited Aug 31 '23 at 14:05

2

Try cleaning maven from upstream by:

mvn -U clean install

edited Aug 31 '23 at 14:05

Penny Liu

15,447
5
79
98

answered Jul 27 '21 at 12:56

Bablu

161
7

score 1 · Answer 16 · answered Aug 19 '16 at 17:59

I also got this error for multiple times when I try to build a new java project.

Below is the step how I got this stupid issue.

Create an empty project, and create new directory src/main/java.
Create the source package net.gongmingqm10.sketch.
Use gradle wrapper, gradle idea to build the gradle stuff for the project.
Add some dependencies in build.gradle file, and gradle build, reimport the project.
Create User.java and School.java in the existing package net.gongmingqm10.sketch
I got the error while I try to use import School in User.java.
Intellij keeps complain can not resolve symbol on import.

Solution:

Build the project first, and mark the main/java as the source root. Create a new directory with the same name net.gongmingqm10.sketch. Move all the files from the old troubling packages to new package.

Root cause:

Directory tree of source code

As you can see from the tree. I got a directory named net.gongmingqm10.sketch. But what we really need is the 3 levels directory: net->gongmingqm10->sketch

But before I finish building my project in Intellij, I create new directory named net.gongmingqm19.sketch, which will give me a real directory with the name net.gongmingqm10.sketch.

When we trying to import it. Obviously, how can intellij import the file under the weired directory with the name a.b.c.

Thanks dude, this was my problem. edit: elaborating... I copied from 1 maven module to another, and the copy flattened the directories. while Intellij looked like it had everything sorted, my folder was in fact "a.b.c" rather than a>b>c. — Qbert, Jul 01 '17 at 21:16

score 1 · Answer 17 · answered Jun 12 '17 at 17:09

@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:

Click on Help -> Edit Custom Properties
Set the property to a larger value; the default is 2500KB idea.max.intellisense.filesize=2500

score 1 · Answer 18 · answered Jul 30 '19 at 15:28

1

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 '19 at 15:28

Adam M. Erickson

53
7

score 1 · Answer 19 · answered Apr 13 '22 at 15:05

1

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 '22 at 15:05

Rajat Goyal

42
3

for me, I only need to restart IDE. – st mnmn Mar 28 '23 at 08:26

score 0 · Answer 20 · answered Dec 09 '16 at 23:02

0

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 09 '16 at 23:02

neoguy

61
8

score 0 · Answer 21 · answered Apr 23 '17 at 00: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.

score 0 · Answer 22 · edited May 01 '17 at 18:04

0

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.

edited May 01 '17 at 18:04

demongolem

9,474
36
90
105

answered May 01 '17 at 17:06

mario

1

score 0 · Answer 23 · edited Jun 05 '17 at 15:28

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.

score 0 · Answer 24 · answered Jan 03 '18 at 18:54

I had this recently while trying to use Intellij to work on NiFi, turned out the issue was that NiFi requires Maven >= 3.1.0 and the version that I'd checked out with (I guess my default) was 3.0.5. Updating the Maven version for the project fixed it, so in some cases Maven version mis-alignment can be a thing to look...I'd guess it's fairly unusual but if you get this far on the thread you're probably having an unusual issue :)

score 0 · Answer 25 · answered Oct 25 '18 at 11:58

0

file-> Project Structure -> Modules, find the module with problems, click it and choose the Dependencies tab in the right side. Click the green plus sign, try to add the jar or libraries that cause the problem. That works for me.

answered Oct 25 '18 at 11:58

SteveHu

82
9

score 0 · Answer 26 · answered Dec 24 '19 at 21:59

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.

score 0 · Answer 27 · answered Jan 29 '20 at 10:42

0

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

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

answered Jan 29 '20 at 10:42

lempesis

1
3

score 0 · Answer 28 · answered May 18 '21 at 15:32

0

My issue was my Maven plugin got disabled after an update. I went to Help -> Find Action... -> Typed in Maven and found that it was "Off". I clicked the toggle switch and after a bit of loading it was re-enabled.

answered May 18 '21 at 15:32

Rjbeckwith

720
8
16

score 0 · Answer 29 · answered May 26 '21 at 13:29

0

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 '21 at 13:29

Bestows In Constructing

311
2
13

score 0 · Answer 30 · answered Oct 25 '21 at 20:24

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.

score 0 · Answer 31 · edited Jan 24 '22 at 13:17

0

I've tried all the complicated methods and they didn't work, since I was too lazy to re-import the project I tried something else. Mine is a gradle project, so I went to my gradle.build file, removed the dependency, refreshed the dependencies, then added the dependency again and refreshed again, the imports started working after that.

edited Jan 24 '22 at 13:17

Dharman

30,962
25
85
135

answered Jan 24 '22 at 13:11

Elen Mouradian

475
1
8
13

Wenbin · Answer 32 · 2017-01-12T02:22:20.260

-1

I had a similar issue with my imported Maven project. In one module, it cannot resolve symbol on import for part of the other module (yes, part of that module can be resolved).

I changed "Maven home directory" to a newer version solved my issue.

Update: Good for 1 hour, back to broken status...

edited Jan 12 '17 at 02:22

answered Jan 11 '17 at 22:16

Wenbin

1
2

Intellij Cannot resolve symbol on import

32 Answers32

Linked

Related