chore(runway): cherry-pick fix: compliance modal appear once on asset page cp-7.74.0

[runway-github]

• fix: compliance modal appear once on asset page cp-7.74.0 (fix: compliance modal appear once on asset page cp-7.74.0 #29201)

Description

On the token details (spot assets) page, tapping Long or Short
when a wallet is OFAC-blocked would open the AccessRestrictedModal
correctly the first time, but pressing either button again would do
nothing — the modal could never be reopened without leaving and
re-entering the screen.

Root cause: TokenDetailsActions sets a navigationLockRef to
true on every button tap to prevent rapid double-navigation. It is
cleared by three paths: screen refocus, navigation state change, or an
explicit resetNavigationLockRef callback passed in from the parent.
When useComplianceGate's gate() detects a blocked wallet it shows
AccessRestrictedModal (rendered at the app root by
AccessRestrictedProvider) and returns early — no navigation occurs,
the screen never blurs, and the external reset was never called. The
lock stayed true permanently, silently swallowing all subsequent
Long/Short presses.

Fix: Added .finally(() => resetNavigationLockRef.current?.()) to
both handleLongPress and handleShortPress in
AssetOverviewContent.tsx. This mirrors what the geo-block path already
does inside closeEligibilityModal. The call is a safe no-op when
handlePerpsAction navigates away, since the focus/state listeners also
clear the lock in that case.

Additionally, AccessRestrictedModal was migrated from the legacy
internal BottomSheet component to the BottomSheet exported by
@metamask/design-system-react-native, which is the single source of
truth for bottom sheets in the codebase. The
shouldNavigateBack={false} prop was also removed — the design-system
BottomSheet does not expose this prop and the modal is rendered at the
app root so no back-navigation is possible regardless.

Changelog

CHANGELOG entry: Fixed an issue where the access-restricted compliance
modal could not be reopened after being dismissed on the token details
page.

Related issues

No issue: bug fix for observed regression on the compliance-gated
Long/Short buttons on the token details screen.

Manual testing steps

Feature: Access-restricted compliance modal on the token details page

  Background:
    Given I am logged into MetaMask Mobile
    And my wallet address is flagged as OFAC-blocked (compliance check returns blocked)
    And I am on the token details page for a token that has a Perps market (e.g. ETH)

  Scenario: user can reopen the compliance modal after dismissing it
    Given I see the Long and Short action buttons

    When user taps the Long button
    Then the access-restricted bottom sheet modal appears

    When user dismisses the modal by tapping the close button
    Then the modal is dismissed

    When user taps the Long button again
    Then the access-restricted bottom sheet modal appears again

  Scenario: user can open the compliance modal via the Short button after a previous dismissal
    Given I see the Long and Short action buttons

    When user taps the Short button
    Then the access-restricted bottom sheet modal appears

    When user dismisses the modal by tapping the close button
    Then the modal is dismissed

    When user taps the Short button again
    Then the access-restricted bottom sheet modal appears again

Screenshots/Recordings

Before

N/A

After

N/A

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.

---

Note

Low Risk
Low risk bug fix that only adjusts button press flow and a modal
implementation; main risk is unintended double-tap navigation if the
lock is cleared too aggressively.

Overview
Fixes an issue where Long/Short on the token details screen could
only open the compliance access-restricted modal once by ensuring the
TokenDetailsActions navigation lock is always released when
useComplianceGate().gate() completes (including non-navigating paths).

Migrates AccessRestrictedModal to use the design-system
BottomSheet component and removes the unsupported shouldNavigateBack
prop. Adds tests to assert repeated Long/Short presses re-invoke
gate() when it resolves without navigating.

^{Reviewed by Cursor Bugbot for commit
5a47cb7. Bugbot is set up for automated
code reviews on this repo. Configure
here.}

[0b88c75](https://github.com/MetaMask/metamask-mobile/commit/0b88c751672d3b14769528aedb5ef13cf3cc3488)

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - PR targets a release branch (release/*)

All E2E tests pre-selected.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chloeYue]

LGTM

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
12 value mismatches detected (expected — fixture represents an existing user).
View details