[Bug]: Initiating a swap from the "All networks" assets view for a token on a different network than the one currently selected results in the token balance being displayed as zero on the swap screen

[sleepytanya]

Describe the bug

Attempting to initiate a swap from the "All networks" assets view for a token on a different network than the one currently selected results in the token balance being displayed as zero. Transaction can't be submitted.

Build https://drive.google.com/file/d/1qhGX0lnrTX47M_7kbqBmhOXTd8HvmflL/view?usp=drive_link

Expected behavior

Screenshots/Recordings

swapTokenBalance.mov

Steps to reproduce

1. Switch to 'All network' view
2. Select token on a different network
3. Start swap

Error messages or log output

No response

Detection stage

On the development branch

Version

dev build

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[gambinish]

Addressed here: 0235189

[sleepytanya]

@gambinish @jonybur
Balance is not 0 but the message about insufficient token balance is shown under the actual token balance. After destination token is selected, the message disappears.

insufficientBalance.mov

[Unik0rnMaggie]

Issue is not present in the qa-3 build.

The balance of the token seems to be updated correctly on the swap screen.

Swap.from.other.network.than.the.one.selected.mov

[gambinish]

I'm about to release another build qa-5. Can we verify that this bug has been fixed, so that we can close this out?

[sleepytanya]

@gambinish
Same behavior as in the previous comment - Balance is not 0 but the message about insufficient token balance is shown under the actual token balance. After destination token is selected, the message disappears. Tx can be succesfully submitted on the correct network:

1.mov

[Unik0rnMaggie]

Confirming same bahavior in qa 5- build:

After destination token is selected, the message disappears:

Screen.Recording.2024-11-21.at.12.56.59.mov

[gambinish]

Thanks, this sounds like a messaging issue that should be a quick fix. Likely still in qa-6, but I can look at fixing this tomorrow

[sleepytanya]

@gambinish

The 'Not enough token' message is not related to the fact that user selects the token on a different network.
It happens for all non-native tokens if swap is initiated from the token details screen, it can be token on the currently selected network as well as token from another network:

Screen.Recording.2024-11-23.at.00.45.35.mov

[Unik0rnMaggie]

Reproduced on qa-7 build, when swapping non native tokens from the token details screen.

The message disappears after selecting the token to swap to

Swap.from.token.details.screen.mov

[gambinish]

This PR should address this issue: #28707 will try to include in the qa-8 build

[Unik0rnMaggie]

Not present in qa-8 build:

Swap.non-native.from.token.details.screen.mov

[gambinish]

Closing, since this seems to be fixed on qa-8