connection.connector.getChainId is not a function #4216
Replies: 11 comments 9 replies
-
|
we are also running into this @Sahitya777 ... looks like a bug. did you create an issue in the wagmi repo? i'd like to upvote it if it's there... thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Hey so basically what I found is that you have to use ssr in this and that will do the trick for you, you dont have to reconnect again and again on reload and there is no writecontract error as well so try that out once. |
Beta Was this translation helpful? Give feedback.
-
|
ah thanks… but we are using vite so it’s all client-side. we may be running into a different issue then. |
Beta Was this translation helpful? Give feedback.
-
|
hey i am also the same issues like r.connector.getChainId is not function |
Beta Was this translation helpful? Give feedback.
-
|
Ton link |
Beta Was this translation helpful? Give feedback.
-
|
Ton link chain blockchair |
Beta Was this translation helpful? Give feedback.
-
|
++++ having same issues as well! |
Beta Was this translation helpful? Give feedback.
-
|
Same issue :( |
Beta Was this translation helpful? Give feedback.
-
|
same issue |
Beta Was this translation helpful? Give feedback.
-
|
following |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone been able to resolve this? @Sahitya777 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I have been able to solve this by using the right config object. I had 2 objects that were playing the role of config, one made with old Wagmi code, and the other made using ReOwn. I was using the config from Wagmi, when the Wagmi component had the config from ReOwn. This, I guess, was at the origin of the bug. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your response! 👏 In my case, I'm using I'll inspect more if it's double config that's happening in my case, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @Adebesin-Cell, we were having the same issue with rainbowkit but it's not happening anymore (3 weeks ago). Did you update viem + wagmi + rainbowkit to it latest version? |
Beta Was this translation helpful? Give feedback.
-
|
Not yet, let me try that, thanks @agualis 👏 |
Beta Was this translation helpful? Give feedback.
-
|
It seems to come from when there is a divergence between the config used by the Wagmi wrapper component, and the config used by transactions (readContract, writeContract). |
Beta Was this translation helpful? Give feedback.
-
|
I had this issue but it seems to be due to the browser wallet silently signing me out of my account, not a wagmi misconfiguration. Once the sign out happens, wagmi starts throwing this error. I suspect that metamask just changed their sign-out delay and now this is happening to many users. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same error and I solved it with the following code: U have to wait until connection will be ready in order to sign messages or use custom hooks |
Beta Was this translation helpful? Give feedback.
-
|
For me, the wagmi config used to be inside the provider component. Moving it outside fixed this |
Beta Was this translation helpful? Give feedback.
-
|
any update? |
Beta Was this translation helpful? Give feedback.
-
So the issue is that I have one base route in my application as /v1 where I have a modal for wallet connects and when the user connects the wallet I send him to other route like /home where the wallet stays connected by connectWagmi({ connector:wagmiConnectors[0] })
But the thing is If i refresh the page the write calls start to fail and give error of connection.connector.getChainId is not a function Idk why it is happening
This is my config
const config = createConfig(
getDefaultConfig({
// Your dApps chains
chains: [baseSepolia],
transports: {
// RPC URL for each chain
[baseSepolia.id]: http(
),
},
);
Beta Was this translation helpful? Give feedback.
All reactions