Description

This PR adds support for universal links from Braze push notification deeplinks. It also removes the interstitial from this source, alongside all trusted sources (carousels, push notifications, Braze push notifications and in-app notifications).

Relevant documentation:
https://www.braze.com/docs/developer_guide/push_notifications/deep_linking?tab=objective-c&sdktab=swift
https://www.braze.com/docs/partners/message_orchestration/deeplinking/branch_for_deeplinking/?tab=objective-c

Changelog

CHANGELOG entry:

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/GE-188

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]

Cold & Hot Start: Deeplink Flow Requirements

1. Open deeplinks without interstitial

Send test notifications with deeplinks from Braze and NaaP

→ Expect: Direct open, no interstitial

2. Open deeplinks with interstitial

Open deeplinks from your notes
Open a deeplink from a QR code (e.g., generated here) pointing to: https://link.metamask.io/trending

→ Expect: Interstitial displayed before opening

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.