MetaMask / MetaMask/metamask-extension

[Bug]: Intermittent Insufficient funds alert when sending token with network fee paid in different token than native

Open
#41,839 4 comments 0 reactions 0 assignees View on GitHub
INVALID-ISSUE-TEMPLATE regression-RC-13.27.0 Sev2-normal team-confirmations type-bug
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

**Describe the bug**

When native token balance is zero and a transaction is performed for ERC20 token, sometimes the intermittent alert for Insufficient funds is displayed, instead of network fee to be paid from ERC20 token.

**Expected behavior**

No insufficient funds intermittent message

**Screenshots/Recordings**

https://github.com/user-attachments/assets/dcd9a22a-faaf-4133-8e6c-5f7d0ab6d386

**Steps to reproduce**

1. Have zero balance of native tokens on Ethereum Mainnet or Linea
2. Simulate transactions for ERC20 token
3. Notice sometimes the alert for insufficient funds is displayed

**Error messages or log output**

```shell

```

**Where was this bug found?**

Internal release testing

**Version**

13.27.0

**Build type**

None

**Browser**

Chrome

**Operating system**

MacOS

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the transaction on Ethereum Mainnet or Linea with zero native-token balance and an ERC20 token, using the version and Chrome/MacOS details provided. Trace the fee and insufficient-funds handling around the intermittent alert; done means the transaction can use the ERC20 token for the network fee without showing an insufficient-funds message.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.