Skip to content

[Bug]: Starting Approval transaction for WETH on Base renders NFT Withdrawal request #32489

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

Open
sleepytanya opened this issue May 3, 2025 · 0 comments
Labels
needs-triage Issue needs to be triaged regression-RC-12.18.0 Regression bug that was found in release candidate (RC) for release 12.18.0 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. team-confirmations Push issues to confirmations team team-swaps-and-bridge For issues with Swaps or Bridging type-bug Something isn't working

Comments

@sleepytanya
Copy link
Contributor

Describe the bug

Starting Approval transaction for WETH on Base renders NFT Withdrawal request. Approval can be confirmed, but the swap fails with the Unknown error: "Internal JSON-RPC error."

Expected behavior

Correct Approval screen is shown

Screenshots/Recordings

weth_approve_base.mov
Image

Steps to reproduce

  1. Connect to a dapp
  2. Switch to Base
  3. Select WETH
  4. Trigger Approval

Error messages or log output

Detection stage

During release testing

Version

12.18.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

@sleepytanya sleepytanya added regression-RC-12.18.0 Regression bug that was found in release candidate (RC) for release 12.18.0 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. team-confirmations Push issues to confirmations team team-swaps-and-bridge For issues with Swaps or Bridging type-bug Something isn't working labels May 3, 2025
@github-project-automation github-project-automation bot moved this to To be triaged in Bugs by team May 3, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity May 3, 2025
@metamaskbot metamaskbot added the needs-triage Issue needs to be triaged label May 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue needs to be triaged regression-RC-12.18.0 Regression bug that was found in release candidate (RC) for release 12.18.0 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. team-confirmations Push issues to confirmations team team-swaps-and-bridge For issues with Swaps or Bridging type-bug Something isn't working
Projects
Status: To be fixed
Status: To be triaged
Development

No branches or pull requests

2 participants