golang/mobile@56e3592 makes it impossible to access current_vm, which means that calling JNI functions directly is no longer available... :-/

The above problem was solved #26815

BTW, to use JNI in init() function, I also tried to use JNI_GetCreatedJavaVMs, but failed due to the below message. Adding #cgo LDFLAGS: -ljvm didn't help since libjvm couldn't be found.

gomobile: go build -buildmode=c-shared -o=/var/folders/b7/w11sqqrx7kx6fqfbn24wdsmh0000gn/T/gomobile-work-277134993/android/src/main/jniLibs/armeabi-v7a/libgojni.so gobind failed: exit status 2                                             
# github.com/hajimehoshi/ebiten/internal/devicescale
../ebiten/internal/devicescale/impl_android.go:25: error: undefined reference to 'JNI_GetCreatedJavaVMs'
clang60: error: linker command failed with exit code 1 (use -v to see invocation)

My understanding is that Seq.setContext (gomobile-bind case) tries to initialize the context and invokes a Go function, but this invocation provokes all the init function before setting the context. Then, in order to solve this issue, we'd need to set the context without Go. Is that correct?

CC @hyangah @timcooijmans

Sorry I missed this issue.

Yes that's the way it works at the moment. This change was needed because older versions of gomobile used reflection that was blacklisted by Android. Do you really have to use init() functions? Can't you use your own initX() functions?

You don't have to bind to an activity, you can also do it from a Service or even from the Application. But I guess that doesn't solve your problem.

Hi,

Do you really have to use init() functions? Can't you use your own initX() functions?

I might not, but other people might. I'm developing a library working with gomobile. If a function uses RunOnJVM, the function can be called from main and after but not from init, and this is not a good user experience.

https://github.com/golang/mobile/blob/35478a0c49da882188b186a3893d45be6ff74327/app/android.go#L72