Does switchNetwork actually return a promise?

[lsbyerley]

gm... I have an async function in my app that performs some updates to the ui when the network is changed by the user. According to the docs, switchNework is supposed to return a promise, but it appears that is not the case. In my function below, the console log statement is logged before the network actually changes.

const onChangeNetwork = async (e, c) => {
  const newNetwork = await switchNetwork(c.id);
  console.log("LOG: newNetwork", newNetwork);
};

// the newNetwork variable is logged immediately and contains an object resembling this: { data: true,  error: undefined}

Has anyone else needed to await the switchNetwork function and perform actions after the network updates?

[tmm]

Just tested out with inject, WalletConnect, and WalletLink connectors and it works fine.

Also, opened a PR to change return type of switchChain from boolean to Chain.

[lsbyerley]

nice.. i'm only using injected provider for my app. If you have time, do you mind posting how you tested this? I'm not sure why mine isn't awaiting the network change and am curious how you verified this

[lsbyerley]

The chainId from the useNetwork hook is still the old network's chainId after awaiting the network change. It seems the networkData from the hook should also have the updated chainId

const [ { data: networkData }, switchNetwork ] = useNetwork();

// On network change via the user changing it
const onChangeNetwork = async (c) => {
  const newNetwork = await switchNetwork(c.id);
  console.log("LOG: this is newNetwork", newNetwork?.data?.id);
  console.log("LOG: this is networkData hook", networkData?.chain?.id);
};

[lsbyerley]

@tmm does this make sense? i can do a workaround in my app, just curious if this is actually an issue or as expected

[tmm]

Looks like a promise to me

https://codesandbox.io/s/magical-kirch-qi06o?file=/src/App.tsx

CleanShot.2022-02-06.at.21.47.01.mp4