-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[Bug]: Importing a custom token does not work #43593
Copy link
Copy link
Open
Labels
needs-triageIssue needs to be triagedIssue needs to be triagedregression-prod-13.35.0Regression bug that was found in production in release 13.35.0Regression bug that was found in production in release 13.35.0team-core-extension-uxCore Extension UX teamCore Extension UX teamtype-bugSomething isn't workingSomething isn't working
Metadata
Metadata
Assignees
Labels
needs-triageIssue needs to be triagedIssue needs to be triagedregression-prod-13.35.0Regression bug that was found in production in release 13.35.0Regression bug that was found in production in release 13.35.0team-core-extension-uxCore Extension UX teamCore Extension UX teamtype-bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for Bug.
Projects
StatusShow more project fields
To be triaged
Describe the bug
When importing a token using token contract address, the message displayed is "token successfully imported", but the token is not displayed in the token list.
This happens for both popular networks and custom networks.
The token can be added using Search on popular networks. If it's enabled and disabled, adding it using token contract displays the same error as here
On custom networks, the search does not find any results and the only option is adding it as custom token, using the token contract.
Expected behavior
Be able to add token using token contract address
Screenshots/Recordings
Screen.Recording.2026-06-16.at.10.42.45.mov
Screen.Recording.2026-06-16.at.10.47.36.mov
Steps to reproduce
Error messages or log output
Where was this bug found?
Live version (from official store)
Version
13.35.0
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response