-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Got "missing r" error when using EAS + Metamask + etherjs #97
Comments
We have met a similat issue recently. This seems related to recent metamask upgrade. |
We have same issues, upgraded to ethers 6.9.0 it seemed to have fixed it, but after a few days I encountered same issue again so it's not consistent. Whats the solution? Whats causing this? Thanks. |
It seems to be caused by Metamask or WalletConnect's latest upgrades. They are working on a fix, so hopefully it will be resolved soon. |
Any updated on this? |
No, unfortunately. Does this still reproduce with the latest MetaMask? |
I also encounter the same issue while deploying a contract with "ethers": "^6.8.1" and metamask extension at this date. Uncaught (in promise) TypeError: missing r ... |
Which contract? |
A custom factory contract, which is not related to eas at all |
also have the same issue using "ethers": "6.7.0", "hardhat": "2.22.4" and MetaMask 11.15.6 Updated: find out solution for me is to use @xiaohou77 So try to use "ethers": "6.13.0" |
@itev4n7 please make sure to post it on Metamask's and ether's repos as well. This issue is unrelated to EAS. |
I have submitted a issue on MetaMask repo: MetaMask/metamask-extension#25032 |
Issue detail
In our dApp https://app.fairsharing.xyz/, when we make an onchain attestaion call, metamask returned the error as below snapshot,
We use EAS + Metamask + etherjs. When we change wallet app to like OKX, it works well.
Who should fix this issue and how?
I found a relative issue ethers-io/ethers.js#3926, seems we have to wait for etherjs to fix?
Or metamask should get this fixed?
Or we have to replace etherjs?
Please help look into this issue, it is blocking many users using our dApp now.
@brycealan @slavik0329
The text was updated successfully, but these errors were encountered: