Description

Fixes a bug where the stablecoin lending empty state CTA was rendered for assets that weren't supported but were supported for the mUSD conversion feature.

Changelog

CHANGELOG entry: fixed bug where the stablecoin lending empty state CTA was rendered for assets that weren't supported but were supported for the mUSD conversion feature.

Related issues

Fixes:

• Github issue: [Bug]: Tapping "Earn" on the asset details page for USDC, USDT, or DAI (mainnet/Linea), after closing the mUSD conversion CTA, consistently causes the app to crash #29504
• Jira ticket: MUSD-725: Stablecoin lending empty state CTA rendered for unsupported tokens (DAI Linea)

Manual testing steps

Feature: Stablecoin Lending Empty State CTA rendering behaviour

  Scenario: user does not see the stablecoin lending empty state CTA rendered
    Given user has Linea DAI balance > $0.01

    When user navigates to Linea DAI asset details screen
    And user dismisses the mUSD conversion CTA banner
    Then user does not see the stablecoin lending empty state CTA

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.