Description

This change aligns MetaMask Mobile’s Send flow with the extension by surfacing first-time recipient interaction and token contract warnings before the user continues to confirmation.

Reason: Users should be explicitly warned when sending to an address they have not interacted with on-chain before, and when the recipient looks like a token contract, so they can double-check the destination.

Solution:

• Added checkFirstTimeInteraction in app/util/transaction-controller/index.ts, using getAccountAddressRelationship from the transaction-controller preview package so semantics match the extension.
• Introduced send-flow alert hooks (useFirstTimeInteractionSendAlert, useTokenContractSendAlert) and an aggregator useSendAlerts that orders alerts (token contract first, then first-time interaction).
• Refactored SendAlertModal to accept multiple SendAlert items with prev/next navigation (design-system ButtonIcon, no “N of M” counter) and per-step acknowledge labels where needed.
• Updated Recipient to open the modal when there are unacknowledged alerts, reset acknowledgement when the recipient changes, and block Review / auto-advance while alert checks are pending.
• Removed the old toAddressErrorAllowAcknowledge path from address validation in favor of the dedicated alert pipeline; token-contract detection moved out of validateHexAddress into the alert hook.
• Added/updated unit tests and locale strings for the new copy and navigation accessibility labels.

Changelog

CHANGELOG entry: Added Send flow warnings for first-time recipient interaction

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/CONF-1016

Manual testing steps

Feature: Send flow first-time recipient

  Background:
    Given I am logged into MetaMask Mobile
    And I am on the Send flow recipient step for an EVM network

  Scenario: user sees first-time interaction alert for a new recipient
    Given I have an externally owned recipient address I have never sent to on this network
    And the recipient is not one of my accounts and is not shown as verified while trust data loads

    When user enters or selects that recipient and taps Review (or equivalent continue)
    Then a warning modal should appear about sending to this address for the first time
    And the modal should show the recipient address in the message

    When user acknowledges the alert (e.g. Continue / I understand as labeled)
    Then the flow should proceed toward confirmation as usual

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.