fix: Ensure root messenger has required function for error reporting

[FrederikBolding]

Description

The root messenger on mobile does not currently have a captureException function passed. This means that any controllers relying on messenger.captureException to record unhandled errors are having their errors swallowed. This PR fixes it by passing in the Sentry captureException function.

Changelog

CHANGELOG entry: Fixed an issue where certain error reporting would not work

---

Note

Low Risk
Low risk: wires existing Sentry captureException into root Messenger/ExtendedMessenger construction; behavior change is limited to enabling error capture for controllers that opt into it.

Overview
Fixes missing error reporting on mobile by importing Sentry’s captureException and passing it into both getRootExtendedMessenger and getRootMessenger in app/core/Engine/types.ts.

This ensures controllers using messenger.captureException can forward unhandled errors to Sentry instead of silently swallowing them.

^{Written by Cursor Bugbot for commit 1617775. This will update automatically on new commits. Configure here.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeAccounts, SmokeConfirmations, SmokeWalletPlatform, SmokeNetworkAbstractions, SmokeNetworkExpansion, SmokeTrade, SmokeIdentity, SmokeMultiChainAPI, FlaskBuildTests
• Selected Performance tags: None (no tests recommended)
• Risk Level: medium
• AI Confidence: 82%

click to see 🤖 AI reasoning details

E2E Test Selection:
The change in app/core/Engine/types.ts adds captureException from @sentry/react-native to both getRootExtendedMessenger() and getRootMessenger() factory functions. These are the root messenger constructors that underpin ALL controller communication in the app.

Why this is medium risk (not high):

• The change is purely additive — it adds an error reporting callback to the messenger, not removing or modifying existing functionality
• No controller initialization order changes
• No state schema modifications
• No messenger action/event list changes
• captureException is a well-established Sentry API

Why broad testing is still warranted:

• Both root messenger factories are foundational infrastructure — every controller's restricted messenger derives from these roots
• If the captureException integration causes any unexpected behavior (e.g., Sentry SDK issues, unexpected exception swallowing, or performance impact), it would affect ALL controller communication
• The root messenger is used across accounts, transactions, networks, snaps, identity, trading, and all other features
• The change touches Phase 1/2 infrastructure (root messenger initialization)

Tags selected:

• SmokeAccounts: Account management uses messenger-based controller communication
• SmokeConfirmations: Transaction/signature flows depend on messenger infrastructure
• SmokeWalletPlatform: Core wallet features use messenger throughout
• SmokeNetworkAbstractions: Network management relies on messenger communication
• SmokeNetworkExpansion: Multi-chain/Solana flows use messenger
• SmokeTrade: Swap/bridge flows use messenger-based controllers
• SmokeIdentity: Profile sync uses messenger infrastructure
• SmokeMultiChainAPI: CAIP-25 session management uses messenger
• FlaskBuildTests: Snaps use messenger for permissions and RPC calls

Tags NOT selected:

• SmokeRamps: Fiat on/off-ramp is more isolated and lower risk for this infrastructure change
• SmokeCard: Card integration is isolated enough
• SmokePerps/SmokePredictions: These are feature-specific and the messenger change is unlikely to specifically break them beyond what SmokeTrade/SmokeWalletPlatform covers

Performance Test Selection:
The change adds captureException to the root messenger constructors. This is an error reporting callback that would only be invoked on exceptions (error paths), not on normal operation. There is no expected performance impact on normal app flows — the captureException function is not called during normal messenger operations, only when errors occur. No performance tests are needed.

View GitHub Actions results

[github-actions]

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud