Hello
I have noticed a recurring issue when switching between Arbitrum One and Arbitrum Nova in browser wallets like MetaMask. If I have both networks added & I switch from Nova to One / vice versa certain dApps either fail to detect the correct chain or misreport the connected network entirely. 
This creates a confusing UX where I believe I’m interacting with Nova (for lower fees), but the app is actually processing requests on Arbitrum One or even defaulting to Ethereum mainnet. 
What makes it tricky is that wallet popups sometimes confirm the right chain ID (42161 or 42170), but the dApp UI does not always catch the network switch instantly unless I do a full refresh or manually reconnect the wallet.
This could be problematic for less technical users who assume they’re transacting on one network but are actually on another especially if the interface doesn’t show the token price impact or fee differences clearly. 
Checked https://docs.arbitrum.io/welcome/get-started-IoT Course guide for reference .
Is this a known limitation of how RPC switching works across L2s, or could Arbitrum-specific best practices be enforced through EIPs or wallet guidelines?
Thank you!! 