Description

We had a Sentry error (getBearerToken - unable to proceed, wallet is locked) caused by TanStack Query refetching social leaderboard and trader profile/positions queries while the wallet is locked.

The root cause is that ReactQueryService wires AppState to TanStack's focusManager, so every app foreground triggers a refetch of all stale queries. Since staleTime: 0 is hardcoded in @metamask/react-data-query, all queries are always stale. If the wallet auto-locked while the app was backgrounded, the refetch on foreground hits getBearerToken → #assertIsUnlocked → throws.

To address this we can gate the enabled prop on selectIsUnlocked in the three affected hooks. TanStack fully pauses a query (no refetch interval, no focus refetch, no reconnect refetch) when enabled: false. On wallet unlock, the Redux selector triggers a re-render and the query immediately resumes.

The updated hooks are:

1. useTopTraders
2. useTraderProfile
3. useTraderPositions
   Cached data continues to be shown while locked, so there is no visual regression.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.