web3modal.connect() catches `undefined` as errors

[johnfrades]

so if the user rejects connecting to metamask

and if theres a pending request and user tries to connect

All of them catches the error but its always undefined. so its quite hard to see what kind of error it throws. is there a way around this?

[german-schneck]

+1

[cfiestas6]

same here

[xzilja]

With stable version 2.0.0 of Web3Modal now released, we are officially dropping support for version 1.x Due to this this issue/pr was marked for closing. It is highly recommended to upgrade as 2.x will be receiving further updates that will enable functionality for some of our newer sdks like auth and push as well as support for WalletConnect v2 (See this post about WalletConnect v1 being deprecated https://medium.com/walletconnect/walletconnect-v1-0-sunset-notice-and-migration-schedule-8af9d3720d2e)

If you need to continue using Web3Modal 1.x and require this feature/fix implemented, we suggest adding it via forking V1 branch.