panic when building with go 1.22 and wails 2.7.1 on Windows about wails HOT 13 CLOSED

I could but as I mentioned it was a fresh VM with fresh Go install and fresh wails install.

from wails.

It could be a mismatch between a 1.21 built CLI and a 1.22 built project. I'm not sure how... perhaps an issue with the Go module cache? Could you please try 1.22 again but make sure you clean out the Go caches:

• go clean -cache
• go clean -modcache
• Install Wails CLI using Go 1.22
• Generate project
• wails build

from wails.

I just reproduced it. Absolutely looks like an issue with Go itself. I'll try open an issue on the Go repo today

from wails.

Ohh (waves hand), I'm no hero...

from wails.

Been tinkering switching between go versions

so "go install wails" with 1.21 creates a good wails CLI (build works)
"go install wails" with 1.22 creates bad wails CLI (panic)

just fyi, not sure if this informs anything you didnt already know.

from wails.

Do you use Goland or VSC? Perhaps if we create a new project using the -ide flag and load it in the IDE, we could run it in debug mode and hopefully get some context about which Go command is causing this.

from wails.

@leaanthony both. We have multiple devs on our team, some use Goland on win, some VSCode.

from wails.

I was also able to reproduce it on macOS. Building wails cli with go1.22.0. It also happens with wails dev just after executing go mod tidy. Manually building the wails app directly with go works also.

The culprit seems to be golang.org/x/tools, after updating it to at least v0.13.0 the wails cli started to be working again, if the cli was built with go1.22.

It seems like the issue has already been reported at the go repo golang/go#64812

from wails.

PR to bump x/tools is up #3244

from wails.

@acastruc would it be possible for you to give the PR #3244 a try?

from wails.

@acastruc would it be possible for you to give the PR #3244 a try?

standby

from wails.

@stffabi fix verified, thanks

from wails.

Released as part of v2.8 👍

from wails.