Skip to content
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

[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

Closed
sleepytanya opened this issue Oct 22, 2024 · 1 comment · Fixed by #28272
Assignees
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

Comments

@sleepytanya
Copy link
Contributor

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

Screenshot 2024-10-22 at 12 30 35 Screenshot 2024-10-22 at 12 30 44 Screenshot 2024-10-22 at 12 35 14
nonce.mov

Steps to reproduce

  1. Enable an account connected to the dApp
  2. Switch to non-enabled account in the MetaMask
  3. Initiate a transaction from the dApp

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

@sleepytanya sleepytanya added type-bug regression-develop Regression bug that was found on development branch, but not yet present in production team-confirmations Push issues to confirmations team labels Oct 22, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Oct 22, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Oct 22, 2024
@sleepytanya sleepytanya added the regression-RC-12.6.0 Regression bug that was found in release candidate (RC) for release 12.6.0 label Oct 23, 2024
@bschorchit bschorchit added release-blocker This bug is blocking the next release Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. and removed release-blocker This bug is blocking the next release regression-develop Regression bug that was found on development branch, but not yet present in production regression-RC-12.6.0 Regression bug that was found in release candidate (RC) for release 12.6.0 labels Oct 23, 2024
@bschorchit
Copy link

@jpuri reported this is not a v12.6 regression so I have updated the label. We'll continue to prioritize a fix for this issue

@jpuri jpuri self-assigned this Oct 29, 2024
github-merge-queue bot pushed a commit that referenced this issue Nov 6, 2024
## **Description**

Use transaction from address to get custom nonce value.

## **Related issues**

Fixes: #28014

## **Manual testing steps**

1. Enable an account connected to the dApp
2. Switch to non-enabled account in the MetaMask
3. Initiate a transaction from the dApp
4. Ensure correct nonce is displayed

## **Screenshots/Recordings**
TODO

## **Pre-merge author checklist**

- [X] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [X] I've completed the PR template to the best of my ability
- [X] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [X] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Nov 6, 2024
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by severity Nov 6, 2024
@metamaskbot metamaskbot added the release-12.8.0 Issue or pull request that will be included in release 12.8.0 label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants