You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When preparing the package to call from swift, the gomobile bind command returns an error.
Here are the logs:
myterminal $ go-bip39 % go get golang.org/x/mobile/cmd/gobind
go: added golang.org/x/mobile v0.0.0-20231006135142-2b44d11868fe
myterminal $ go-bip39 % gomobile bind -target ios -o ../frameworks/bip39.xcframework
gomobile: /Users/myterminal/go-workspace/bin/gobind -lang=go,objc -outdir=/var/folders/hp/rh26j25gz_7vm0000gp/T/gomobile-work-825612255/ios -tags=ios github.com/tyler-smith/go-bip39 failed: exit status 1
functions and methods must return either zero or one values, and optionally an error
second result value must be of type error: func github.com/tyler-smith/go-bip39.GetWordIndex(word string) (int, bool)
second result value must be of type error: func github.com/tyler-smith/go-bip39.GetWordIndex(word string) (int, bool)
second result value must be of type error: func github.com/tyler-smith/go-bip39.GetWordIndex(word string) (int, bool)
Not sure how to modify the issue @tyler-smith to create a workaround.
Is there a workaround? Some of the logs suggested that the crypto library had a corrupted go.sum.
The text was updated successfully, but these errors were encountered:
kcw-grunt
changed the title
🐜[Bug Report] Error when using Gomobile: , GetWordIndex return wrong type
🐜[Bug Report] Error when using Gomobile: , GetWordIndex returns wrong type
Nov 1, 2023
kcw-grunt
changed the title
🐜[Bug Report] Error when using Gomobile: , GetWordIndex returns wrong type
🐜[Bug Report] Error when using Gomobile: func GetWordIndex returns wrong type
Nov 1, 2023
Problem
When preparing the package to call from swift, the
gomobile bind
command returns an error.Here are the logs:
Not sure how to modify the issue @tyler-smith to create a workaround.
Is there a workaround? Some of the logs suggested that the crypto library had a corrupted go.sum.
The text was updated successfully, but these errors were encountered: