You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the previous version, before calling the eth_sendRawTransaction method, Metamask also called eth_getTransactionCount to update its account nonce.
Since Version 12.10.1, this no longer happens, and the transaction fails because of wrong nonce.
Expected behavior
eth_getTransactionCount should be called before eth_sendRawTransaction to update Metamask's account nonce
Screenshots/Recordings
No response
Steps to reproduce
Send two transactions with the code provided. The first one succeeds if the account is new because the nonce is 0.
The following transactions fail because the nonce sent by Metamask is always 0.
Error messages or log output
Detection stage
In production (default)
Version
12.10.1
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
This is how I'm calling the eth_sendTransaction from my JavaScript code:
Describe the bug
In the previous version, before calling the eth_sendRawTransaction method, Metamask also called eth_getTransactionCount to update its account nonce.
Since Version 12.10.1, this no longer happens, and the transaction fails because of wrong nonce.
Expected behavior
eth_getTransactionCount should be called before eth_sendRawTransaction to update Metamask's account nonce
Screenshots/Recordings
No response
Steps to reproduce
Send two transactions with the code provided. The first one succeeds if the account is new because the nonce is 0.
The following transactions fail because the nonce sent by Metamask is always 0.
Error messages or log output
Detection stage
In production (default)
Version
12.10.1
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
This is how I'm calling the eth_sendTransaction from my JavaScript code:
In previous versions of Metamask, this opened the browser extension, I confirmed, and the transaction got sent to the node accordingly.
Severity
This bug doesn't allow users to send any transaction
The text was updated successfully, but these errors were encountered: