Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
1.7.4 - Uncaught Error: User closed modal
See original GitHub issueas reported in https://github.com/NoahZinsmeister/web3-react/issues/454, the 1.7.4 release of @walletconnect/ethereum-provider has a regression. when a user closes the qr modal, there’s an unhandled Uncaught Error: User closed modal
see https://web3-react-lsff62x8m-noahwz.vercel.app/ for a repro
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:9 (3 by maintainers)
Top Results From Across the Web
WalletConnect Modal Close throws error - Moralis Forum
Basically, I'm trying to get WalletConnect login/logout functionality working is react, pure dapp without email login.
Read more >@walletconnect/web3-provider - npm
Disable QR Code Modal. Use your own custom qrcode modal and disable the built-in one. const provider = new WalletConnectProvider({ infuraId: ...
Read more >react-modal | Yarn - Package Manager
Accessible modal dialog component for React.JS ... Need feedback to push a new version of react-modal forward. See issue #881.
Read more >Untitled
WPForms Challenge experience is improved for new users. ... Changed - Adjusted an error message for the Locked Field modal when attempting to...
Read more >SportsPress Pro Changelog - ThemeBoy Support
Tweak - Use Google Maps in front end only to prevent errors in admin. Fix - Tournaments scrambling and auto-winner ... Fix -...
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 Free
Top 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
yes i’m still observing this in 1.7.8 too
Fixed on v1.7.5