96

I am writing a project using the Go language with GoLand IDE by Jetbrains.

While writing the code, GoLand shows me an error message such as "unresolved reference" when the reference do exist and that the program compiles and runs correctly.

Here is a similar (but simpler) example of some code that I have found here on stackoverflow (Go - append to slice in struct) to reproduce this issue.

The same error message appears even though I have implemented the methods just a few lines above.

package main

import (
    "fmt"
)

type MyBoxItem struct {
    Name string
}

type MyBox struct {
    Items []MyBoxItem
}

func (box *MyBox) AddItem(item MyBoxItem) {
    box.Items = append(box.Items, item)
}

func main() {

    item1 := MyBoxItem{Name: "Test Item 1"}
    item2 := MyBoxItem{Name: "Test Item 2"}

    box := MyBox{}

    box.AddItem(item1)
    box.AddItem(item2)

    // checking the output
    fmt.Println(len(box.Items))
    fmt.Println(box.Items)
}

box.AddItem(item1) and box.AddItem(item2) are marked red as an error. If I move my cursor above it, it says unresolved reference "AddItem". Yet the code compiles and runs. And as this was the solution to an other stackoverflow question, I do not think that the code is wrong. Furthermore I cannot find any mistakes in it.

enter image description here

[EDIT: I load the code from a remote server and edit it locally on my private pc. After finishing my changes, I upload it to the remote server (using GoLands tools like "Browse remote host") and build and compile it there. After trying it out locally with the very same code, the error message sometimes is there and sometimes not. I am totally confused]

David
  • 971
  • 1
  • 5
  • 4
  • I couldn't reproduce the problem, running GoLand 2019.2.5. However, I think that if you use `box := &MyBox{}` or `box := new(MyBox)` will "fix" that. Since `AddItem` is a `(box *MyBox)`. – Inkeliz Jan 01 '20 at 21:59
  • thanks for the answer @inkeliz . I tried both variants but no difference. – David Jan 01 '20 at 22:06
  • 1
    Same issue on version 2020.1.4 – Amin Shojaei Jul 26 '20 at 11:53
  • I've had this issue but for external package, `go mod vendor` solved it (just copy the modules to the local folder). This does not answer OP's specific issue but this was the first link I came across for my issue so adding this here for my future self, sorry. – Seraf Sep 29 '22 at 14:35
  • I had this issue after deleting the `go.mod` file by mistake and then undoing the delete. Invalidate Cache helped – Tom Sep 30 '22 at 08:55
  • Same issue on version 2022.2, windows, and wsl. Unfortunately, none of the answers worked for me. – Andromeda Oct 17 '22 at 06:59
  • The fix for me was to go to menu FILE | Invalidate Caches... and click on `Invalidate and Restart`. It will re-index caches and all references will be resolved. per: https://stackoverflow.com/a/61356467/5540365 – SammyRNYCreal Jul 13 '23 at 13:38

23 Answers23

168

I experienced a similar issue, but it was a lot more prevalent. Even things like fmt.Printf() were showing as unresolved. Was able to resolve the issue by going to File -> Invalidate Caches / Restart.

phemmer
  • 6,882
  • 3
  • 33
  • 31
32

I found best way to fix this issue.

  1. close your project and IDE
  2. go to your project directory
  3. remove ./.idea
  4. try to open it again

woops woops, fixed

Edit : better way try to use this one in Goland Menu
file -> repair IDE it will be refresh index module

panapol-p
  • 535
  • 4
  • 8
24

Today I faced that problem and I fixed it by enabling go module integration. For that Settings -> Other Settings -> Go Modules then enable go modules integration. This will work if you using go modules in your project.

Oliver
  • 27,510
  • 9
  • 72
  • 103
Temuujin Dev
  • 692
  • 2
  • 8
  • 20
  • This solved it for me in GoLand. I used VSCode for the same project but did not have this problem and I am not actually sure why. – fanbondi Mar 30 '23 at 09:46
14

I'm using go module and it's solved by:

  • Deselect Preferences->Go->GOPATH->Use GOPATH that's defined in system environment
  • File->Invalidate caches / Restart
Tomer Shetah
  • 8,413
  • 7
  • 27
  • 35
Benjamin Huo
  • 141
  • 1
  • 2
  • The problem occurs again if I generate a vendor directory by go mod vendor, and it will disappear after I remove the vendor directory – Benjamin Huo Apr 04 '21 at 03:04
10

I'm a bit late to the answer lol but incase anyone is still running into this, all I did was delete the .idea file and reloaded the project on GoLand (by clicking File -> Open -> file location). Did the trick for me.

sofshant
  • 183
  • 1
  • 9
  • 1
    Make sure that you create a backup of your .idea folder since it contains some local environment IDE settings (Go version, etc). – s0xzwasd Sep 06 '21 at 14:23
  • Thank you very much, I was about to abort and switch to vscode. It seems that this tip worked for me. – Camilo Bernal Feb 26 '22 at 19:19
  • 2
    This is what I had to do. None of the other steps (fix ide, delete cache, reinstall) worked. – Michael Sep 18 '22 at 13:02
8

I just removed the project from Goland and re-create it from existing files. It was weird but it worked.

koooyooo
  • 81
  • 1
  • 2
6

I cannot reproduce the issue in GoLand 2020.2. I suggest upgrading to it.

If that doesn't fix the issue then you can take the following steps to investigate the issue:

  • Is your project using Go modules or the traditional GOPATH?
  • If it's using GOPATH, have you enabled indexing of GOPATH under Settings/Preferences | Go | GOPATH?
  • If it's using Go modules, check to see that the support is enabled under Settings/Preferences | Go | Go Modules and then use Alt+Enter | Sync packages of‍‍ <project>
dlsniper
  • 7,188
  • 1
  • 35
  • 44
  • 3
    I can still reproduce it in 2020.2 – Reven Jul 23 '20 at 09:38
  • How? More details would help us understand your problem and replicate it to either provide a solution or fix any problems we may have on our side. – dlsniper Jul 25 '20 at 11:12
  • @disniper same problem. My project is in `go/src/project/test.go` and I keep getting this error for everything in the `github.com/thedevsaddam/govalidator` package – Amin Shojaei Jul 26 '20 at 11:56
  • 1
    @AminShojaei is your project using Go modules or the traditional GOPATH? If it's using GOPATH, have you enabled indexing of GOPATH under Settings/Preferences | Go | GOPATH? If not, is Go modules support enabled under Settings/Preferences | Go | Go Modules and then use Alt+Enter | Sync packages of . If neither of these solve the problem, then please open an issue on our tracker at https://youtrack.jetbrains.com/issues/Go – dlsniper Jul 27 '20 at 05:16
  • @disniper That's right. Git module solved my problem. thanks – Amin Shojaei Jul 27 '20 at 06:19
5

For Mac users, i solved this by setting Custom Tags to 'unix'. In Preferences > Go > Build Tags & Vendoring. In the Custom Tags, input unix.

enter image description here

I'm using GoLand 2022.1.2

abetobing
  • 159
  • 1
  • 2
4

For me the issue was the version of Golang, I had been using go1.19 which threw unreferenced errors with .Close methods, switching back to an older version go16.15 helped me resolve this issue.

Satya
  • 1,569
  • 8
  • 13
  • 1
    Same issue with me, I have to switch to go1.18.7 and solved this problem. – Chengcheng Zhang Oct 26 '22 at 12:58
  • 1
    Refer to this answer, [jetbrains-Unresolved-reference-Close-for-os.File](https://youtrack.jetbrains.com/issue/GO-13454/Unresolved-reference-Close-for-os.File), add `unix` tag to File | Settings | Go | Build Tags & Vendoring | Custom tags in 2022.1.4 version. And it worked for me. – Runstone Jan 06 '23 at 11:37
3

Today face the same problem using GoLand 2021.3 MacOS.

Fixed it with go to File Menu -> Repaire IDE...

Then it will automatic fixing issues

iamyusuf
  • 157
  • 2
  • 9
2

I had a similar issue for gin.WrapH function utils.go. Tried the Override File Type option for utils.go in local module path which changed the file as a Go file but had a little cross sign where a tooltip marked that the file is excluded from compilation. The error Unresolved reference only went away when I selected the file, navigated to File -> File Properties -> Associate with File Type -> Register new file type association, and chose Go files

Junaid
  • 3,477
  • 1
  • 24
  • 24
1

No option from other comments helped me. I had to switch GO SDK version in Setting -> Go -> GOROOT. Goland automatically downloaded 1.16 beta 1 version and it worked.

1

In Goland preferences, if you're using the Global GOPATH, check the option "Index entire GOPATH" and hit apply.

Victor Cui
  • 1,393
  • 2
  • 15
  • 35
  • like magic, I had the problem, tried the removing cache, then delete .idea folder, finally found this one, should be the final answer. – Cyberience Mar 03 '22 at 05:16
1

I had the same issue, I did try invalidates cache, but that did not work.

But the thing worked is just add a below line in your idea.properties file. And then restart IDE.

# custom GoLand properties (expand/override 'bin/idea.properties')
idea.max.intellisense.filesize=100000

This is because, Goland does not index huge packages. But you can force it to do that.

ARKhan
  • 1,724
  • 22
  • 30
0

I had the same problem and it got fix weirdly.So I installed and opened project in vscode in order to continue coding.It started installing a extension called gopls. After installation completed I returned to GoLand to close project, but I waited for indexing to complete.Suddenly references were green !

  • Opening it VSCode must've cleared the GoLand caching somehow, and re-indexed your code. File > Invalidate Cache/Restart... is the better way to do it – James Oct 26 '20 at 09:07
0

Goland version 2020.1: I opened a folder with subfolders of golang projects and goland didn't recognize dependencies. I solved this problem setting Project GOPATH

  1. ctrl + alt + s
  2. Go > GOPATH
  3. Click on plus button + In Project GOPATH
  4. Add your golang's project folder, example: ~/projects/my-golang-projects
Gudari
  • 287
  • 1
  • 16
0

I faced the same issue when I do bazel run //:gazelle, I fixed this issue by doing bazel sync (Bazel -> Sync -> Sync Project with BUILD Files). But you should have the below settings. GOPATH Setup Go Module Setup

(This fix is for Goland IDE, Mac. Of course we should add GOPATH in .bash_profile or .zshrc)

Chella M
  • 392
  • 1
  • 2
  • 15
0

I had the same issue with aws go sdk, changing the Custom Properties (Help -> Edit Custom Properties) helped me. here is the reference to the JetBrains thread https://youtrack.jetbrains.com/issue/GO-5029

idea.max.intellisense.filesize=10000
idea.max.content.load.filesize=20000

Restart the IDE to let the changes take effect.

Kunal
  • 125
  • 1
  • 5
0

I had been using go1.19 which threw unreferenced errors with .Close methods. I download the GoLand 2022.2.4 package and install, issue has been solved.

0

In my case, I fixed it by running go mod tidy in the console.

kintsukuroi
  • 1,332
  • 16
  • 15
0

In my case go mod was 1.18 and IDE indexed my project with 1.19. At Preferences -> GOROOT I selected Go 1.18 and problem solved.

0

If your code compiles and runs, you only need to check "Enable Go modules integration" flag ( IDE ultimate version): enter image description here

neverEugene
  • 69
  • 10
-4

I solved it by reinstall Go to D:\go, then reset Go sdk.