serialize stx transactions navigation params

[m-aboelenein]

🔘 PR Type

What kind of change does this PR introduce?

Fix for errors thrown by parsing errors while passing transactions between the send-stx screen and the confirm-stx-tx / confirm-ft-tx screens

• Bugfix
• Enhancement
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no API changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

📜 Background

failure to navigate to the stx confirm screens without visual response on what went wrong

Issue Link: https://linear.app/xverseapp/issue/ENG-2410/cant-send-stx-and-sip-10-tokens

🔄 Changes

stx transactions are serialized then deserialized when being passed as navigation params

Impact:

• Explain the broader impact of these changes.
• How it improves performance, fixes bugs, adds functionality, etc.

✅ Review checklist

Please ensure the following are true before merging:

• Code Style is consistent with the project guidelines.
• Code is readable and well-commented.
• No unnecessary or debugging code has been added.
• Security considerations have been taken into account.
• The change has been manually tested and works as expected.
• Breaking changes and their impacts have been considered and documented.
• Code does not introduce new technical debt or issues.

[linear]

ENG-2410 Can't send stx and sip-10 tokens

Send STX screen || Send sip-10 tokens || Send STX NFT screen:

made sure I built the extension properly

not able to send stx or other sip-10 tokens, due to an app state error, it doesn't have the STX address in state

The issue is present on the latest develop, not present on production (web-store build)

This issue is a release-blocker

Network response when clicking Next button in the mentioned Send screens:

image.png

011e1028-994e-457b-8a3c-66ee8f459819

[DuskaT021]

left a comment in the linear ticket ENG-2410

[DuskaT021]

tested it can be merged

[teebszet]

lgtm