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]: Unable to send erc20 from a normal address, when recently receiving asset. #29218

Open
snowkidind opened this issue Dec 14, 2024 · 6 comments
Labels
external-contributor regression-prod-12.5.1 Regression bug that was found in production in release 12.5.1 Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. team-assets team-bridge type-bug

Comments

@snowkidind
Copy link

Describe the bug

From what I gather there are two places that keep independent balances of the same ERC20 asset. For instance if you access the "Send" from the eth page and select a token versus if you select the token and then hit send. The former will say zero balance and disallow sending and the latter will reflect the latest balance. BUT apparently it still disallows sending because if you go to the latter to send erc20, the send button is stuck on disabled although you are able to add all the proper form elements.

Metamask Extension on Chrome + Ledger connection

Expected behavior

When I have an asset both balance locations should reflect current balance

Screenshots/Recordings

No response

Steps to reproduce

I dont know what you guys have been doing lately but the entire send interface appears to be garbage, the entire form thing is just bizarre. its been nearly impossible for an advanced user to use your software lately.

Error messages or log output

Detection stage

In production (default)

Version

12.5.1

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

Ledger

Additional context

No response

Severity

Unable to send erc20 from a normal address, when recently receiving asset.

@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Dec 14, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Dec 14, 2024
@metamaskbot metamaskbot added external-contributor regression-prod-12.5.1 Regression bug that was found in production in release 12.5.1 labels Dec 14, 2024
@MetaMask MetaMask deleted a comment Dec 16, 2024
@DanielTech21 DanielTech21 added Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. team-confirmations Push issues to confirmations team labels Dec 16, 2024
@DanielTech21
Copy link

Hi @snowkidind

Thank you for bringing this to our attention.

Our team will review it and provide you with more information soon.

@vinistevam vinistevam added team-bridge team-assets and removed team-confirmations Push issues to confirmations team labels Dec 16, 2024
@danjm
Copy link
Contributor

danjm commented Dec 16, 2024

@snowkidind could you share screenshots of what you are seeing?

@snowkidind
Copy link
Author

@snowkidind could you share screenshots of what you are seeing?

I will when I get a chance, might be a couple of days

@snowkidind
Copy link
Author

I have made a video displaying my issues in real time. Is there a non-doxxed place I can submit this?

@alfeng6
Copy link

alfeng6 commented Dec 19, 2024

you can email us directly:

[email protected] and [email protected]

@snowkidind
Copy link
Author

ok sent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external-contributor regression-prod-12.5.1 Regression bug that was found in production in release 12.5.1 Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. team-assets team-bridge type-bug
Projects
Status: To be fixed
Status: To be fixed
Development

No branches or pull requests

6 participants