-
Notifications
You must be signed in to change notification settings - Fork 20
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
Demo version with v4.0.0 is not working on device #72
Comments
Demo works fine on iOS Simulator / Device with metro config replaced with : |
App works with Crypto-browserify for auth and all web3 actions. We have : So either we use react-native-quick-crypto and we can not use Mobil device. Is there any other packages we can use for crypto injection ?
|
Try this way
I also tried to customize
|
Hi @ryukato , I'm facing the same issue. |
**PROBLEM **
We are trying web3auth react native and found your demo version.
https://github.com/Web3Auth/web3auth-react-native-sdk/tree/master/demo/rn-expo-example
We tried to use it with the latest version of web3auth-react-native. (v4.0.0) as the package.json is not referring to the latest :
https://github.com/Web3Auth/web3auth-react-native-sdk/blob/master/demo/rn-expo-example/package.json
The version is working fine on iOS Simulator but is not working on iOS / Android Device using expo.
(we did not tried bare workflow and do not intend to eject expo)
Error shown is :
ERROR Error: react-native-quick-crypto is not supported in Expo Go! Use EAS (
expo prebuild
) or eject to a bare workflow instead., js engine: hermesWe tried to remove react-native-quick-crypto from metro.config.js to react-native-crypto but it triggers other issues.
ERROR TypeError: Cannot read property 'seed' of null, js engine: hermes
** EXPECTED BEHAVIOUR **
A working demo version with v4.0.0 on iOS Simulator & Device.
The text was updated successfully, but these errors were encountered: