Open
Description
Describe the bug
- Inconsistency in the transaction history when viewed from different networks (not sure if that is within the scope as we have an open bug for that)
- If the first submitted transaction is STX, all subsequent txs are submitted as STX on networks that do not support STX. If the first tx is not STX then I can send regular txs on different networks
- I noticed it for BNB only but the first swap has NaN instead of fiat value in simulation for the BNB token (the NaN is also on Erik's video)
- When
Settings -> Advanced -> STX
are disabled, I can't send regular transaction on any network, the confirmation is stuck after tappingConfirm
button
Expected behavior
Screenshots/Recordings
iOS (fresh install, regular tx is submitted is STX after first STX tx):
https://www.loom.com/share/14f45d0f6eb6463283202ae00bfc0951?sid=833f1253-5d78-4b65-a09a-85eeefea09a3
Android (the same behavior as iOS - just to confirm that we also get stuck tx after sending STX, while already having several successful txs):
https://www.loom.com/share/06942b8f3e12481bb887db5905cabad9?sid=d51622e2-5874-4e77-bf29-3ee5746b0acc
Android, STX Off, regular tx stuck on Confirmation screen:
https://www.loom.com/share/35958d98d2404f62bddb4ddaa1be7833?sid=d1346f76-181c-4616-ba10-d0bb5508e6f4
Steps to reproduce
- Connect to PancakeSwap
- Start / submit a swap
Error messages or log output
Detection stage
On a feature branch
Version
7.43.0 (1656)
Build type
None
Device
iPhone 15, Samsung S24 Ultra
Operating system
iOS, Android
Additional context
No response
Severity
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
To be fixed
Status
To be triaged