I'm running into an issue with reverse bindings similar to this.
My project structure is like:
mobile/
└── pkg
└── example
├── android
│ └── javatest.go
└── testmobile.go
*testmobile.go:*
package example
import (
"mobile/pkg/example/android"
)
func
Ok. I fixed it.
For anybody interested, here's how I solved it.
On the Go side, I extended my exported function by adding "ctx
content.Context" as a parameter (i e "func Hello(ctx content.Context).
On the Java side, I'm then passing the mobile context as follows (this is a
React Native app, so
Yea. Turns out that was indeed the issue. I tried accessing a method that
didn't actually exist.
Unfortunately, your code doesn't work either. It leads to a segmentation
violation/nil pointer error.
I suspect one needs to somehow get the right context from the Java side.
Question is how.
I
On Wednesday, April 24, 2019 at 2:34:34 PM UTC+2, Mark Bauermeister wrote:
>
> I'm currently experimenting with Gomobile Reverse Bindings (my hope is to
> eventually be able to call getFilesDir(), so I can save my SQLite3 DB on
> mobile) and it is, quite literally, driving me insane.
> I've
