-
Notifications
You must be signed in to change notification settings - Fork 18k
x/mobile: ambiguous import error when running go mod tidy
#62415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do you have any insights? @dmitshur |
The go directive in x/mobile is set to 1.17. Given by now only Go 1.21 and 1.20 releases are supported per policy, let's fix this by bumping to a newer Go language for the module: one of 1.18, 1.19 or 1.20. |
Ah OK, thanks. I'll send a CL soon. |
Change https://go.dev/cl/525095 mentions this issue: |
This reverts these commit: * 7f0a86f. * b615aaf. Reason: Test failures. See golang/go#62415
By the way, from the error message
I couldn't reach the current solution. The URL seems outdated. Would it be possible to get a better error message for this? |
Another mystery thing is
so EDIT:
Ah, so if go.mod says go1.17, does this mean |
Sorry it's a bit confusing. There's a good description at https://go.dev/ref/mod#graph-pruning. Given this is only relevant to older Go versions that aren't supported by now, I don't think there's anything to other than to move forward. Thanks. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run
go mod tidy
in gomobile. The gomobile version is 52620a4a7557849149770d52fd7b580cb3cbd1aeWhat did you expect to see?
No errors
What did you see instead?
Of course
go mod tidy -compat=1.17
worked, but is there a good solution to fix this?The text was updated successfully, but these errors were encountered: