Fix: get app dir from native part to initialize Gno's structures #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a crash when I try to run the gnoboard app on Android and on some iOS devices.
The Gno configuration struct
BaseOptions
needs adataDir
path to create files. The defaultHomeDir()
function provided intm2/pkg/crypto/keys/client/common.go
to get that path doesn't work on mobile and causes apanic
, because some environment variables are not set on mobile.The
HomeDir
function is called every time thetm2/pkg/crypto/keys/client
subfolder is imported because of the global variableDefaultBaseOptions
that callsHomedir
. To avoid the call of theHomeDir
function that calls apanic
, we duplicatedBaseOptions
in gnomobile, so thetm2/pkg/crypto/keys/client
is no more imported and we provided it the app container path directory from the Android/iOS native parts.This PR also updates the
go.mod
to use the latest version of Gno that fixes the ambiguous import of thebtcd
dependencies.