Describe the bug

Users can enter a state where they are able to initiate an NFT send on a different network than the NFT belongs to.

This occurs because we now display NFTs from all chains the user holds assets on, rather than filtering by the currentChain from GNS.

There are two entry points into the NFT send flow:
1. NFT Detail Screen – If a user taps “Send” from this screen, we proactively switch to the correct network on their behalf.
2. NFT Grid View (Send Button) – This is where the bug occurs. When users initiate the send flow from the main NFT grid, the app does not enforce or switch to the correct network, allowing them to unintentionally attempt to send the NFT on the wrong chain.

Expected behavior

In the send flow, users should only see NFTs that belong to the currently selected network.
NFTs from other networks should not be visible or selectable unless the user explicitly switches to that network first.

Screenshots/Recordings

Steps to reproduce

1. Add an account that holds NFTs on a specific network (e.g., Polygon, Ethereum, etc.).
2. From the main NFT Grid View, tap the Send button (i.e., enter the send flow via flow WEBGL dies on ubuntu #2).
3. Observe that NFTs from multiple networks are listed, regardless of the currently selected network.

Error messages or log output

Detection stage

In production (default)

Version

12.16.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

Sev1