-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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
x/mobile/cmd/gomobile: unclear error when codesigning fails #11488
Labels
Milestone
Comments
The top half of that message (up to |
rakyll
changed the title
x/mobile/cmd/gomobile: Unclear error when codesigning fails
x/mobile/cmd/gomobile: unclear error when codesigning fails
Jul 1, 2015
CL https://golang.org/cl/12002 mentions this issue. |
Thank you! |
imWildCat
pushed a commit
to imWildCat/go-mobile
that referenced
this issue
Apr 10, 2021
Fixes golang/go#11488. Change-Id: I1ff2ca25dd1013d603d6f60d1e8f6e5c58c5b0ee Reviewed-on: https://go-review.googlesource.com/12002 Reviewed-by: David Crawshaw <crawshaw@golang.org>
imWildCat
pushed a commit
to imWildCat/go-mobile
that referenced
this issue
Apr 11, 2021
Fixes golang/go#11488. Change-Id: I1ff2ca25dd1013d603d6f60d1e8f6e5c58c5b0ee Reviewed-on: https://go-review.googlesource.com/12002 Reviewed-by: David Crawshaw <crawshaw@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
x/mobile
rev golang/mobile@3522bcc, go tip:go version devel +117ddcb Tue Jun 30 17:59:02 2015 +0000 darwin/amd64
Running
gomobild build -target=ios golang.org/x/mobile/example/basic
failed for me:Unfortunately that error output doesn't indicate the root cause of the build failure.
Running with
-x
shows that the command that failed wasxcrun xcodebuild -configuration Release -project /var/folders/69/cstplpp51jz6f9_5m_m__3gh0000gq/T/xcodeproject167976650/main.xcodeproj
. When I ran that by hand, the error message was a little more clear:It would be good if the output from
gomobile build
included the full output fromxcrun xcodebuild
.The text was updated successfully, but these errors were encountered: