Problem using walletconnect connector

[shaifvier]

I use the use-wallet component on my react dapp. I have two connectors configured, a default one (injected) for metamask and another one for walletconnect. Any action or transaction that uses Metamask (injected) works perfectly, but whenever I want to use walletconnect I get errors after any simple web3 request.

"Uncaught TypeError: this.send is not a function....." Every web3 request that works using Metamask fails on walletconnect. I am using infura as the rpc for walletconnect and working on the Rinkeby testnet for my tests. Could it be an specific version of my dependencies? I am using the latest available version of use-wallet through npm.

Thanks in advance.

[Clearwood]

I am encountering the same problem I am using the Goerli testnet and Infura as a JSON RPC endpoint as well

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.4729 ETH (160.0 USD @ $338.34/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Chat
• $848,344.12 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 266 years, 1 month from now. Please review their action plans below:

1) aneilpatel05 has applied to start work (Funders only: approve worker | reject worker).

looks like an issue with walletconnect integration. I will set up the application and try to replicate it. 2) deeayeen has been approved to start work.

Hey, had a similar issue and solved it, would be happy to take a look at this for you.

Learn more on the Gitcoin Issue Details page.

[Clearwood]

Pls message me on Twitter @KenoBudde to get access to our dApp in case that helps you with pinpointing the problem.

[shaifvier]

Ok. Found a workaround. Indeed, the problem is related to dependencies. If you are using web3 functionality with the wallet provider, check that web3, web3-utils and web3-core versions are lower than 1.3.0. In my case I reverted to 1.2.11 for every web3 package and walletconnect started to work flawlessly.

[gitcoinbot]

@deeayeen Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@deeayeen Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@deeayeen Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@deeayeen Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] reminder (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 0.4729 ETH (172.95 USD @ $367.99/ETH) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Chat
• $892,079.73 more funded OSS Work available on the Gitcoin Issue Explorer

[cinnabarhorse]

I had this issue today and struggled with it all day. In the end, I discovered that my Infura key had been rate limited, which was causing WalletConnect to fail

[builderyj]

I encountered the same problem today, is there a solution now? I tried to set the web3, web3-utils and web3-core versions to 1.2.11 or 1.3.0, but unfortunately none of them worked

[Clearwood]

I encountered the same problem today, is there a solution now? I tried to set the web3, web3-utils and web3-core versions to 1.2.11 or 1.3.0, but unfortunately none of them worked

We reverted Web3.js to 1.2.11

[builderyj]

I encountered the same problem today, is there a solution now? I tried to set the web3, web3-utils and web3-core versions to 1.2.11 or 1.3.0, but unfortunately none of them worked

We reverted Web3.js to 1.2.11

Yes, after I unified the versions, I did not install the @walletconnect/web3-provider dependency library.

[elmariachi111]

can confirm. Works with [email protected] the line that causes this behaviour is (close to): https://github.com/ethereum/web3.js/pull/3649/files#diff-d25786686c1053b786cc2626dc6e048675050593c0ebaafbf0814e1996f22022R166

[linxux]

Any update for this issue? And any other solution instead downgrade the version of web3?

[builderyj]

Any update for this issue? And any other solution instead downgrade the version of web3?

Follow the previous discussion to solve the problem

[FortisFortuna]

It is still an issue. I had to "web3_for_walletconnect": "npm:[email protected]" in package.json, then import Web3_For_WalletConnect from 'web3_for_walletconnect';

Was also having problems with the events for the sendTransaction() method. Reverting to 1.2.11 as above fixed it.