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
Currently, when a user has an unapproved transaction pending, popups for subsequent transactions initiated from a dApp are not displayed.
If user clicks on a MM budge the notification for the test dapp transaction is shown. After rejecting the fist tx, user can click on MM badge again and see / reject / approve all unapproved dapp transactions.
In some cases after rejecting the first transaction MetaMask shows an error (second video).
sleepytanya
changed the title
[Bug]: The notifications for the transactions initiated from a dapp are not shown if user has an unapproved transaction (initiated form test dapp)
[Bug]: The popup for the transactions initiated from a dapp are not shown if user has an unapproved transaction
Jun 17, 2024
Specifically, if you check the MetaMask popup (in your initial video, it's just behind your main chrome window), do you see these subsequent transaction/approval requests?
Describe the bug
Currently, when a user has an unapproved transaction pending, popups for subsequent transactions initiated from a dApp are not displayed.
If user clicks on a MM budge the notification for the test dapp transaction is shown. After rejecting the fist tx, user can click on MM badge again and see / reject / approve all unapproved dapp transactions.
In some cases after rejecting the first transaction MetaMask shows an error (second video).
Related issues:
#25397
#25393
Slack discussion links:
https://consensys.slack.com/archives/C03ETQA9EPK/p1695933147044299
https://consensys.slack.com/archives/C03ETQA9EPK/p1695932531166009
Expected behavior
Screenshots/Recordings
badge.mov
err.mov
Steps to reproduce
Error messages or log output
No response
Version
12.0.0
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: