…27738)  ## **Description**  Part of the analytics cleanup workstream ([#26686](#26686)). Delivers [PR C1](#26812): migrate `useMetrics` to `useAnalytics` in hardware wallet, wallet recovery, onboarding-adjacent, and related UI (~27 files). - **Ledger / Bluetooth hardware:** `LedgerConfirmationModal`, `LedgerConnect` (`Scan`, entry), and `ConnectHardware/SelectHardware` now call `useAnalytics` from `app/components/hooks/useAnalytics/useAnalytics` instead of `useMetrics`. - **QR hardware:** `ConnectQRHardware` (container + `Instruction`), `AnimatedQRScanner`, and `QRSigningDetails` use the same hook swap; event names and `MetaMetricsEvents` / builder usage stay as before. - **Wallet recovery (web3auth-owned views):** `RestoreWallet`, `WalletRestored`, and `WalletResetNeeded` (+ tests) migrated to `useAnalytics`. - **Post-onboarding settings:** `OnboardingSuccess/OnboardingGeneralSettings`, `OnboardingSuccess/OnboardingSecuritySettings` (+ test) migrated. - **Other touchpoints in scope:** `ExperienceEnhancerModal`, `NftGrid` and `NftGridItemActionSheet` tests—aligned with the C1 slice that includes onboarding-adjacent and shared UI still on legacy metrics. - **Tests:** `jest.mock` targets point at `useAnalytics`; mocks use `createMockUseAnalyticsHook` from `app/util/test/analyticsMock`. Where builders were referenced from tests, imports use `AnalyticsEventBuilder` from `app/util/analytics/AnalyticsEventBuilder` instead of `MetricsEventBuilder`. No change to which events fire or their payloads—this is an API migration only, consistent with prior analytics refactors (e.g. [PR A2 — split types from MetaMetrics](#26988)). ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: #26812 Refs: #26686 ## **Manual testing steps** N/A — refactor-only; behavior and analytics events are unchanged. Unit tests cover updated mocks and components. ## **Screenshots/Recordings**  ### **Before** N/A ### **After** N/A ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.   --- > [!NOTE] > **Medium Risk** > Mostly a hook/API swap, but it touches user-facing hardware wallet and recovery/onboarding flows and can subtly change analytics payloads or break tracking if the new hook differs from `useMetrics`. One NFT tracking event (`WALLET_ADD_COLLECTIBLES`) also gains additional properties, changing event data. > > **Overview** > Swaps analytics wiring across Ledger/QR hardware wallet UI, wallet recovery views, and onboarding success settings to use `useAnalytics` instead of `useMetrics`, including updating imports and call sites. > > Updates unit tests to mock `useAnalytics` consistently via `createMockUseAnalyticsHook`/`AnalyticsEventBuilder`, and adjusts one NFT event (`MetaMetricsEvents.WALLET_ADD_COLLECTIBLES`) to include extra properties in its payload. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit aee6674. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>

Uh oh!

PR C1: migrate useMetrics to useAnalytics in HW Wallet, Wallet Recovery, Onboarding, web3auth (~21 files) #26812

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions