Description

When the user was not authenticated in the v2 Ramps native flow, BuildQuote was navigating directly to EnterEmail, completely skipping the VerifyIdentity screen. The screen existed and was registered in the router but was never wired into the unauthenticated path.

Changes:

• VerifyIdentity.tsx (NativeFlow): exported V2VerifyIdentityParams and createV2VerifyIdentityNavDetails, added useParams to receive amount/currency/assetId from BuildQuote, and forwarded those params to EnterEmail on submit
• BuildQuote.tsx: when the user is not authenticated, now navigates to VerifyIdentity instead of EnterEmail
• Updated tests and snapshots accordingly

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/TRAM-3273?atlOrigin=eyJpIjoiMGQ5ZmE1ZmYxMmVlNGQyOWI4ZDBjYThlMDkzNDMzNDIiLCJwIjoiaiJ9

Manual testing steps

Feature: Verify Identity screen in v2 Ramps native flow

  Scenario: user continues as unauthenticated
    Given the user is on the Ramps BuildQuote screen
    And the user is not authenticated (no existing token)

    When user presses the Continue button on a native provider quote
    Then the Verify Identity screen is shown

    When user presses the Continue button on the Verify Identity screen
    Then the Enter Email screen is shown with the correct amount/currency/assetId params

Screenshots/Recordings

Before

BuildQuote -> EnterEmail (VerifyIdentity skipped)

After

BuildQuote -> VerifyIdentity -> EnterEmail -> OtpCode -> routeAfterAuthentication

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.