Skip to content

[QA] Corresponding destination token sometimes appears only after manual search, not by default #4028

Description

@agodlevska

Describe the current behavior in detail

Environment:

Steps to Reproduce:

  1. Prepare to send SUI from Sui (Suiet) to Arbitrum (MetaMask)
  2. Observe the default list of available tokens before interacting with the search bar.
  3. Type the name of the corresponding token (e.g., "suш") into the search bar.

Expected Results: The corresponding token (wrapped or native equivalent of the selected source token) should be prioritized and displayed by default in the destination token list.

Actual Results: The corresponding destination token is missing from the default suggested list when the modal opens, forcing the user to manually search for it.

Attachments/Notes

Screen.Recording.2026-04-28.at.10.01.37.mov

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions