Explain an empty Manage Tokens search result

[j0ntz]

Description

Manage Tokens now says when a search matches nothing.

Searching Manage Tokens for a contract address the wallet's token list does not carry rendered a bare scene: no rows, no message, and the "Add Custom" button hidden behind the keyboard. That frame is pixel-identical to a search that is not matching at all, so nobody can tell "this token is not in the list" from "the search is broken".

That ambiguity is what this PR's task is about. QA filed 1217587221308437 against the Manage Tokens contract-address search, that search was fixed in EdgeApp/edge-react-gui#6170, and a later QA pass attached another blank-scene screenshot. This run reproduced the QA steps on current develop and the search works: the full MOG contract address 0xaaeE1A9723aaDB7afA2810263653A34bA2C21C7a returns the Mog row, and so does UNI's 0x1f9840a85d5af5bf1d1762f925bdaddc4201f984. What the blank frame cannot show is which of the two causes produced it.

MOG makes the gap easy to hit. It is not a built-in token: it is absent from edge-currency-accountbased's compiled Ethereum list and from the info-server token payload, so it only exists in an account after someone adds it through "Add Custom". On an account that never did, an address search for it correctly returns nothing, and says nothing.

The fix renders a centered message in the list's empty slot while a search is active. A search that matches nothing now says so, and points at the control that adds the token.

Asana: https://app.asana.com/0/1215088146871429/1218117826000799

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

• Tested on iOS device
• Tested on Android device
• Tested on small-screen device (iPod Touch)
• Tested on large-screen device (tablet)

[j0ntz]

📸 Test evidence

mog full address finds mog

unknown address says no match

Captured by the agent's in-app test run (build-and-test).

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.