Description

When navigating to the send flow from QR scanner with a predefinedRecipient, the param was being lost when the user transitioned between screens within the nested Send stack navigator (e.g., Asset → Amount).

Root cause: handleSendPageNavigation passes predefinedRecipient via navigate("Send", { screen, params: { predefinedRecipient } }). React Navigation v5 delivers these params to whichever nested screen is the initial target. When no asset is pre-selected (QR scanner flow), the initial screen is Asset. When the user picks an asset and navigates to Amount, the useSendScreenNavigation hook called navigate("Send", { screen }) without forwarding params - so predefinedRecipient was lost.

Fix: Update useSendScreenNavigation to forward the current screen's route.params when navigating between screens within the nested Send navigator. This ensures all navigation params (including predefinedRecipient) survive intra-navigator transitions.

Changelog

CHANGELOG entry: Fixed QR code scanned recipient address not being forwarded through the send flow

Related issues

Fixes: CONF-1307

Manual testing steps

Feature: QR Scanner predefined recipient in send flow

  Scenario: user scans a QR code with a valid address and completes send
    Given the user is on the wallet home screen

    When user opens the QR scanner and scans a valid address QR code
    Then the send flow opens starting at the Asset selection screen
    And after selecting an asset, the Amount screen is shown
    And pressing Continue skips the Recipient screen and submits with the scanned address

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.