[Bug]: Swap from Uniswap, Swap from Swap flow

[sleepytanya]

Describe the bug

1. No STX screen when swapping on networks with STX enabled (mainnet + BNB) when swap is initiated from the dapp. For the swaps initiated from Swap flow the STX screen is shown on both networks
2. On BNB for the first swap NaN is shown
3. I only tried 3 networks - mainnet, BNB and Polygon. On Polygon and BNB the token balance is shown as 0 on Confirmation screen
4. On Polygon I was unable to submit native token swap with the alert on Confirmations screen suggesting that account doesn't have enough POL to pay for gas (account has 35 POL)
5. I was able to swap non-native tokens on Polygon
6. The build is slow and it is hard to say if some issues like txs are not displayed in the Activity screen are bugs or they can be attributed to the degraded performance. I wasn't able to verify some other UI elements (like toast notifications / tx details) because of screen unresponsiveness and screen automatic switch to another tab sometimes.
7. The Approval request always had Spending Cap value blurred. I was able to tap on it, could you please have a look if Spending Cap values look correct to you
8. For STX swaps the tx details screen displayed gas fee as Undefined

https://www.loom.com/share/426390fe3f994bd3acd2ad711ebcb9f2?sid=6e6f2a62-d206-4dca-b8cf-683143e59921

https://www.loom.com/share/fea549d6945c4624aa80b785c0213d75?sid=176a8f07-cd66-4e3e-868d-8759c39f993d - this can be skipped, I'm just confirming if there STX screen for Swaps from within the wallet on BNB (we do get STX screen)

9. STX are enabled, transaction on a network without STX support is submitted as regular transaction:

bnb_op.mov

Expected behavior

Screenshots/Recordings

Steps to reproduce

1. Go to Uniswap
2. Start Swap tx

Error messages or log output

Detection stage

On a feature branch

Version

7.43.0

Build type

None

Device

Samsung S24 Ultra

Operating system

Android

Additional context

No response

Severity

No response

[dan437]

Hi, can someone from the @MetaMask/confirmations team please have a look at why there is a $NaN value on the Confirmation page?