[Bug]: A mismatch between the network selected and the tokens displayed when a custom RPC URL is added

[sleepytanya]

Describe the bug

Upon adding a custom RPC URL while the extension is active on a different network and the "Current Network" view is chosen, the interface transitions to the "Popular Networks" view. The tokens displayed are associated with the previously selected network. Refining this behavior to ensure that the view and the tokens displayed align with the newly selected network would greatly improve the user experience by providing a more seamless and accurate reflection of the user's current network setting

Also present in 12.11.0

Expected behavior

The view and the tokens displayed align with the newly selected network and the user's current network setting.

Screenshots/Recordings

12_10.mov

12_11.mov

Steps to reproduce

1. Select Current network view
2. Add custom RPC URL for a network different than currently selected one

Error messages or log output

Detection stage

In production (default)

Version

12.10.1

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[danjm]

This does not seem to present signficant risk to the user, so we will not block v12.10.1 roll out on it.

[gambinish]

I will take a look at this