Description

Fixes Perps WebSocket connectivity issues when:

1. App returns from background — after a few minutes in background, the OS silently kills the WebSocket but PerpsConnectionManager still reports isConnected = true. No code path detected the stale connection or triggered reconnection.
2. WiFi/network drops and restores — toggling WiFi, airplane mode, or losing cellular signal kills the WebSocket, but since the app stays in active state, the existing AppState-based recovery (if any) never fires.

Root Cause

PerpsConnectionManager had no lifecycle awareness of:

• React Native AppState transitions (background → foreground)
• Network connectivity changes (offline → online via @react-native-community/netinfo)

Arthur's prior fix (#26334) made StreamChannel.ensureReady() connection-aware to avoid blind polling on slow connections, but it only helps when a reconnection is already in progress (isConnecting = true). After background resume or WiFi restore, nobody triggers the reconnection in the first place.

Fix

• AppState listener — on active, cancels any pending grace period and runs validateAndReconnect()
• NetInfo listener — tracks wasOffline state; on offline → online transition, runs validateAndReconnect()
• validateAndReconnect(context) — shared method that sends a lightweight ping() health check to the active provider. If the ping fails (stale WebSocket), marks the connection as lost and triggers reconnectWithNewContext({ force: true }) which reinitializes the controller, validates with a fresh health check, and preloads all stream subscriptions.
• Cleanup — both listeners are properly removed in cleanupStateMonitoring()

Changelog

CHANGELOG entry: Fixed Perps WebSocket not reconnecting after app resume from background or WiFi/network toggle

Related issues

Fixes: connectivity loss after backgrounding app, WiFi off/on not recovering Perps data

Manual testing steps

Feature: Perps connection recovery

  Scenario: App returns from background after several minutes
    Given the user has navigated to the Perps trading screen
    And the user has an open position

    When the user backgrounds the app for 3+ minutes
    And the user returns to the app
    Then the Perps WebSocket reconnects automatically
    And positions, prices, and account data resume updating

  Scenario: WiFi is toggled off and back on
    Given the user is viewing live Perps positions
    And WiFi is connected

    When the user turns WiFi off
    And waits a few seconds
    And turns WiFi back on
    Then the Perps WebSocket reconnects after network is restored
    And live data resumes without requiring navigation away

  Scenario: Airplane mode is toggled
    Given the user is on the Perps trading screen

    When the user enables airplane mode
    And then disables airplane mode
    Then the connection recovers and live data resumes

Screenshots/Recordings

Before

After backgrounding or WiFi toggle, Perps shows stale data with no automatic recovery. User must navigate away and back to restore the connection.

After

Connection automatically recovers via health-check ping and force reconnection. Live data resumes within seconds.

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.