Description

This PR cleans up verbose Sentry error logging in the Perps feature. Many of these errors were logged for debugging connection issues but don't represent actual user-impacting problems. The changes focus on graceful handling during transient states (reconnection, initialization) and fixing a WebSocket race condition.

Key Issues Fixed:

1. WebSocket Race Condition - Added transport ready gate to ensure WebSocket is in OPEN state before subscriptions
   • Prevents "WebSocket subscribe error: undefined" during initialization
   • Prevents subscription failures during reconnection window
2. Subscription Client Race Condition - Added async gates (await ensureSubscriptionClient()) to guarantee client availability before use. Throws are preserved as safety assertions - they should never fire with the async gates in place. Exception: restoreSubscriptions() uses graceful return since it's invoked during reconnection when transport readiness is still being established.
3. CLIENT_NOT_INITIALIZED - Added null-safe provider access method for UI components
4. Market Pattern Validation - Added input normalization for HIP-3 DEX patterns

Technical Changes:

• Added ensureTransportReady() method to HyperLiquidClientService that awaits SDK's transport.ready() before marking connection as CONNECTED
• Made initialize() async with 10s timeout for WebSocket handshake
• Updated handleConnectionDrop() to await transport ready before restoring subscriptions
• Added ready check in restoreSubscriptions() before re-establishing subscriptions
• Updated all 17 call sites in HyperLiquidProvider to await async initialization

Approach:

• Uses SDK's built-in transport.ready() method - no SDK modification required
• Async guarantees with safety assertions (throws preserved as bug indicators)
• Graceful handling only in restoreSubscriptions() (legitimate transient state during reconnection)
• Existing restoreSubscriptions() handles reconnection automatically

Changelog

CHANGELOG entry: Fixed Perps WebSocket race conditions and error handling during reconnection/initialization states

Related issues

Reduces verbose Sentry logging for:

• WebSocket subscribe/connection errors during init and reconnection
• METAMASK-MOBILE-5502 - Subscription client not available
• METAMASK-MOBILE-4RN7 - CLIENT_NOT_INITIALIZED
• METAMASK-MOBILE-4XVE - Market pattern invalid

Note: Event counts in Sentry are inflated due to verbose debug logging during development.

Manual testing steps

Feature: Perps error handling during reconnection

  Scenario: User views Perps while offline then connects
    Given user has the app open on Perps tab
    And device is offline

    When device reconnects to network
    Then Perps data should load without errors
    And no error toasts should appear

  Scenario: User switches accounts rapidly
    Given user is viewing Perps positions

    When user switches accounts multiple times quickly
    Then app should not crash
    And positions should update for final selected account

  Scenario: App backgrounded then foregrounded
    Given user is viewing Perps positions
    And app is backgrounded for a few minutes

    When user brings app to foreground
    Then positions should refresh correctly
    And no error toasts should appear

Screenshots/Recordings

Before

Verbose Sentry errors logged during WebSocket reconnection and initialization states (these were debug-level issues, not user-impacting)

After

• WebSocket subscriptions only occur after transport is in OPEN state
• Graceful degradation during transient states (debug logging instead of Sentry errors)
• Subscriptions automatically restored via restoreSubscriptions() mechanism

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.