[Bug]: Unable to send erc20 from a normal address, when recently receiving asset. #29218
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
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.
The text was updated successfully, but these errors were encountered: