Description

Problem

The account picker was failing to select accounts in certain UI flows due to InteractionManager.runAfterInteractions() blocking critical selection callbacks. When the UI was busy with animations or interactions, the callback queue would be deferred indefinitely, leaving users unable to switch accounts.

Root Cause

The issue only occurred when AccountSelector was rendered inline within active screens (such as BuildQuote or SwapsAmountView) rather than as a modal (like the NavBar). In complex UI contexts with ongoing animations (keypad interactions, focus effects, loading states, etc), the interaction queue never clears, causing runAfterInteractions() callbacks to wait indefinitely.

Works: Navbar → Modal AccountSelector (interaction queue clears on navigation)
Broken: BuildQuote, SwapsAmountView inline AccountSelector (perpetual interaction queue from parent animations, not sure the EXACT animations causing the blockage)

Solution

Removed the InteractionManager wrapper around the account selection logic in EvmAccountSelectorList

Impact

• Account selection now works reliably across all UI states
• Maintains existing functionality while fixing the blocking behavior
• The InteractionManager was originally added for performance optimization unintentionally blocked user experience

Changelog

CHANGELOG entry: null

Related issues

Fixes: #16942

Manual testing steps

1. Go to this Swaps or Deposit screens
2. Constantly switch accounts and observe that account selection is no longer blocked
3. The app MAY crash when quickly switching account but that is due to another issue logged here

Screenshots/Recordings

Before

NA

After

NA

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.