[Bug]: When an account hasn't been enabled in the Permissions, attempting to initiate a transaction from a dApp results in the transaction being created from an enabled account but with the nonce value matching the account selected by user #28014
Labels
release-12.8.0
Issue or pull request that will be included in release 12.8.0
Sev1-high
High severity; partial loss of service with severe impact upon users, with no workaround.
team-confirmations
Push issues to confirmations team
type-bug
Describe the bug
When an account hasn't been enabled in the
Permissions
, attempting to initiate a transaction from a dApp results in the transaction being created from a different, enabled account. Interestingly, the nonce value corresponds to the non-enabled account selected in MetaMask.If a transaction is created with a nonce that is too low, it fails and generates errors. Conversely, if the nonce is set too high, the transaction remains in a
Pending
state without displaying any error messages.Expected behavior
Screenshots/Recordings
nonce.mov
Steps to reproduce
Error messages or log output
No response
Detection stage
On the development branch
Version
develop
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
The text was updated successfully, but these errors were encountered: