Nami Wallet crashes when signing tx due to a buggy code
See original GitHub issueSummary
A buggy code added 1.5 months ago is causing a crash when signing transactions.
Details
This piece of code does not seem to perform anything, but it is causing a crash when signing a tx.
Loader.Cardano.TransactionUnspentOutput.new()
.output()
.amount()
.coin()
.compare();
Loader.Cardano.TransactionUnspentOutput.new
requires two arguments, but this code provides zero. Therefore, the app crashes.
Please remove this buggy code
Appendix
fyi, here is the console error when Nami Wallet crashes:
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Nami Wallet Transaction Failed - Community Technical Support
Hi, I have a Nami wallet, and it shows my current balance but every time I try to do any transaction is says...
Read more >Issues · berry-pool/nami - GitHub
Nami Wallet is a browser based wallet extension to interact with the Cardano blockchain. ... Nami wallet signing transactions with the wrong keys....
Read more >Signing a Tx with Nami wallet - Cardano Stack Exchange
i get: {code: -1, info: 'Inputs do not conform to this spec or are otherwise invalid.'} My question is: is something wrong in...
Read more >Nami
Nami is a browser based wallet extension to interact with the Cardano blockchain and is non-custodial. It can be used to send and...
Read more >Nami wallet fails every time : r/cardano - Reddit
Also I would suggest checking your wallet balance with another wallet. You're probably spamming a bunch of unnecessary transactions when 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
Yes fixed the issue already. Just have to wait until chrome store approves it.
Thanks for the prompt response.
This issue is blocking my development. I hope that the new version will be released soon.
As a side note, I believe that this issue would have been easily prevented if the repo uses TypeScript or a similar type-checking system. One possible way to prevent similar issues is to migrate to TypeScript. This migration process can be done incrementally and therefore does not hurt the development.
(btw, @kk-kien and me are the same person)