`ethersContext.signer` does not change when metamask account changes about eth-ui HOT 5 CLOSED

pushed a change to update the signer field on change

from eth-ui.

I think this is also related to the useSignerAddress hook because with the fix implemented in #178, running the test scenario again, logging ethersContext.signer when it changes:

Initial connect:

After changing accounts, the signer on ethersContext is correct but the result of useSignerAddress is still outdated:

from eth-ui.

I've been experiencing this issue for many days now and didn't know what was going on.

But it came with another symptom, and I kept blaming Metamask for it: my transactions would fail with a Metamask error saying RPC Error: Invalid parameters: must provide an Ethereum address

Only accidentally I discovered that it was occurring when I was changing accounts in metamask:

The header account was always updating correctly, so I never considered to check the context values.
But indeed the ethersContext.signer would keep the old address.

Only a page reload would fix the mismatch...

from eth-ui.

@ShravanSunder I've looked into it just a bit and it seems to be a bug in web3-react, rather than in eth-hooks

from eth-ui.

@stephancill have you found a suitable workaround?

For anyone having this issue and looking for a quick fix:

Create a helper like

export const getCurrentSigner = async () => {
  const ethereum = window.ethereum;
  // eslint-disable-next-line @typescript-eslint/no-unsafe-argument
  const provider = new ethers.providers.Web3Provider(ethereum);
  await provider.send('eth_requestAccounts', []);
  return provider.getSigner();
};

It works without making any other changes than this:

Instead of
contract.functionCall(arg1, arg2)
you can
contract.connect(await getCurrentSigner()).functionCall(arg1, arg2)

from eth-ui.