Description

This PR updates mobile to consume @metamask/compliance-controller@2.1.0 and wires the mobile compliance setup to use the configured Compliance API URL.

The reason for this change is to bring mobile onto the latest compliance-controller release that supports explicit API URL configuration and shared wallet-blocked selectors. That support is needed for the broader compliance work so mobile can resolve compliance checks through build configuration instead of relying only on the controller package’s environment fallback.

The solution bumps the compliance-controller dependency, passes COMPLIANCE_API_URL into ComplianceService, adds the URL to mobile build configuration, and updates the mobile selector wrapper to use the core batch blocked-wallet selector. Tests were updated to cover the configured API URL wiring and the EVM case-insensitive address matching behavior from the released controller package.

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.