Yoroi extension on Chrome is stuck with white screen on launch
See original GitHub issue・ Yoroi Chrome version is 4.7.4 ・ OS: Macbook (other user has reported on different OS too, see forum link below) ・ User has lost his recovery phrase and is dependent on his spending password to create new wallet or attempt any reinstalls ・ Not a unique case (few users have reported it before, eg: here) ・ The behaviour has been present for months ・ Console Error:
618.bundle.js:1 rolling back Lovefield query for
KeyDerivation
Address
AddressMapping
EncryptionMeta
UtxoTransactionInput
UtxoTransactionOutput
TokenList
Token
CertificateAddress
Certificate
Transaction
Block
AccountingTransactionInput
AccountingTransactionOutput
RootDerivation
PurposeDerivation
CoinTypeDerivation
Bip44Account
Bip44Chain
CanonicalAddress with error {}
N @ 618.bundle.js:1
yoroi_bde52cb3.bundle.js:1 AdaApi::refreshTransactions error: {
"stack": "Error: [BigNumber Error] Not a number: undefined
at i (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/46.bundle.js:2:53381)
at new W (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/46.bundle.js:2:44480)
at chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/544.bundle.js:1:1281533
at chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/544.bundle.js:1:1281597
at Array.map (<anonymous>)
at he (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/544.bundle.js:1:1280437)
at async chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/544.bundle.js:1:1282152
at async N (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/618.bundle.js:1:45470)
at async me (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/544.bundle.js:1:1282058)
at async Te.refreshTransactions (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/yoroi_868f51f5.bundle.js:1:2308)",
"message": "[BigNumber Error] Not a number: undefined"
}
error @ yoroi_bde52cb3.bundle.js:1
yoroi_bde52cb3.bundle.js:1 WalletStore::refreshWalletFromLocalOnLaunch {
"message": "api.errors.GenericApiError: undefined",
"name": "l",
"stack": "l: api.errors.GenericApiError: undefined
at Te.refreshTransactions (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/yoroi_868f51f5.bundle.js:1:3111)
at async i._method (chrome-extension://ffnbelfdoeiohenkjibnmadjiehjhajb/js/yoroi_ef4bde61.bundle.js:1:145790)",
"id": "api.errors.GenericApiError",
"defaultMessage": "!!!An error occurred, please try again later.",
"values": {}
}
error @ yoroi_bde52cb3.bundle.js:1
yoroi_ef4bde61.bundle.js:1 Uncaught (in promise) l
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Yoroi blank page after Alonzo upgrade - Cardano Forum
I am unable to access the Yoroi UI from any browser on the Mac. ... Yoroi extension on Chrome is stuck with white...
Read more >Yoroi wallet stuck at white page : r/cardano - Reddit
When I open Yoroi wallet it get stuck at "loading" page. There is just white page with Yoroi logo. It worked just fine...
Read more >Top 7 Ways to Fix Google Chrome White Screen Error on ...
Top 7 Ways to Fix Google Chrome White Screen Error on Windows 10 · 1. Close Google Chrome Completely · 2. Turn off...
Read more >Yoroi Wallet Not Working? [Ways to Fix] - ViralTalky
Uninstall and Reinstall ... You can try uninstalling the Yoroi Wallet app and wait for thirty seconds, then download it again and see...
Read more >How to Fix Google Chrome White Screen Error on Launch
Step 1: Click on the three dots at the top, click on More Tools, and select Extensions in the submenu. Extension Settings Min....
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
@cardanoz , the version
4.7.500
is now in the stores, might take some time for auto-updates to kick in. Test it please again if possible after making sure the new version is being used. Will really appreciate any feedback on whether the issue changed in any way.He has confirmed it now and seems to have fixed it! !! thank you very much! !!🙇♂️🙇♂️🙇♂️