[tron-wallet-snap] Errors for Tron Native and TRC20 token transactions

[sgextcsi]

Tested on Main Branch of Metamask Mobile and Extension

Observations for Tron transaction are different for Tron Native token and TRC20 tokens, details as below:

For Tron native token, Sent operations works fine - the TRX amount is successfully transferred from one account to another, balance is updated in both accounts, but the Sent activity remains in Pending state. Although I found that the Received activity is displayed and Confirmed.
Transaction hash: https://tronscan.org/#/transaction/04077cbc58ee7df1770907be9c416f48202e39712e68ef978070755e14b43e74

For Tron TRC20 token, Sent operations fails -

• the TRC20 token (SUN or USDT) amount is not actually transferred from one account to another
• the SUN or USDT balance is not updated in any of the accounts
• but in tronscan I find that the status is confirmed, Resources Consumed and a certain amount of TRX is reduced in account balance,
• the Sent activity remains in Pending state
  Transaction hash (SUN transaction): https://tronscan.org/#/transaction/1c086bea45e2b173883722314d3f8a4573ea11d28879d4b7841d85a1bb503380

Transaction hash (USDT transaction): https://tronscan.org/#/transaction/f1c9f8c4f74d53ddd08cccf5c30d74246216941fc6c9e96ed927d11fde974834

For Tron TRC20 token, Swap operations also fails -

• the TRC20 token (USDT) amount is not actually swapped between tokens
• the USDT and TRX balance is not updated in my account
• but in tronscan I find that the status is confirmed (but the Result says: FAILED-OUT OF ENERGY), Resources Consumed and a certain amount of TRX is reduced in account balance,
• the Swap activity displays as Pending state in list page and Unconfirmed in details page

Transaction hash (USDT transaction): https://tronscan.org/#/transaction/a4c4cbfdbb02e14b562085578a6aa5ccd8e1565922aedab70e46a7a40a0a9c1b

[sgextcsi]

Also note that, if we open the open the wallet in another browser profile or in another device, the Pending TXs are lost

[ulissesferreira]

This causes: MetaMask/metamask-mobile#28006

[markspedev]

@sgextcsi have you been able to resolve this issue?