-
Notifications
You must be signed in to change notification settings - Fork 9
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
react-native compatibility #71
Comments
Could provide a minimal reproducible example that triggers the errro? This is a go error, currently bitbox02-api-js is transpiled with gopherjs
|
Thanks for not closing the issue. So, I created this repository here. At first it was not showing the original error, because of this problem:
after adding this workaround
I managed to force the above mentioned error. Hope it helps. Would be great if Bitbox is also react-native compatible |
Thanks for the repo ❤️ !! The transpiled go code is just so big 🙈 Running This person has a similar issue with a big lib also using react native babel/babel#12231 For some reason I don't get stuck anymore at 98% building, but the emulator can't connect to the debugger.. here I am afraid I just don't have enough experience with react native. :( cc @benma |
If support cannot be guaranteed on the native level for react, do you think including a webview and loading the interface through it would be a viable workaround? I will probably try it soon if there's no native solution by then. |
I was already expecting while reading the
README.md
that I won't be lucky with react-native.But I tried the sample integration and already hit the first error that happens somewhere here:
bitbox02-api-go.js
:ERROR Error: runtime error: makeslice: len out of range
Is react-native compatibility planned or do you suggest including a webview as a workaround?
The text was updated successfully, but these errors were encountered: