react-native app crash -> ethers.Wallet.createRandom({locale:'ko'})
See original GitHub issueHi
Thanks for making the library
I am developing a wallet and I want to use the mnemonic code in Korean, but it works well in debug mode, but when I exit the debug mode, the app is terminated.
its work !
const wallet = ethers.Wallet.createRandom({locale:'en'});
but its not working…
const wallet = ethers.Wallet.createRandom({locale:'ko'});
What can I do to prevent the app from crashing?
Any help would be thanks.
English used Google Translate.
Thanks
Issue Analytics
- State:
- Created 3 years ago
- Comments:33 (17 by maintainers)
Top Results From Across the Web
React Native slow / freeze whet i call ethers.Wallet ...
I have test this in both IOS and Android and was able to create a HD Wallet instantly. To use bip39 in React...
Read more >React Native App crash upon review… - Apple Developer
I've recently submitted twice a new app and got it refused twice as well because the app crashed in the hands of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello again, this mnemonicToSeed which uses pbkdf2 and takes around 10 second to user access wallet when he have passwords for security perpose obviously. but when i create a wallet and connect it to provider. this function runs 3 time which increases time 10 to 30 seconds. why is that? couldn’t it converted to one time run from create wallet to connect to provider.
The issue with the Korean (Hangul) wordlists is unfortunately not something that can be solved on Android with broken implementations of normalize. There is no safe way to even detect the issue, since
try..catch
cannot trap it; the browser simply crashes.I’m closing this now, and hopefully the user base on platforms still using the broken String implementation on Android dwindles. This issue is over a year old, so maybe it already has. 😃