feat(SDKConnectV2): add toasts for non-success states

[ffmcgee725]

Description

This PR adds to the current implementation of MetaMask Connect toasts to ensure that error messages are displayed in the Wallet when a user rejects a request or when other errors occur during the request lifecycle.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/WAPI-825

Manual testing steps

Feature: MM Connect toasts for non-success states

  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

Screen.Recording.2025-11-13.at.11.22.04.mov

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.

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

Show an error toast when bridge responses contain JSON-RPC errors and use the connection id for error notifications; add tests for success/error paths.

• SDKConnectV2:
  • Connection (services/connection.ts): On bridge response, detect JSON-RPC errors (error in payload) and call hostApp.showConnectionError(this.info); otherwise call showReturnToApp(this.info). Always forward payload to client.
  • Host App Adapter (adapters/host-application-adapter.ts): Change showConnectionError signature to conninfo? and use conninfo.id when provided (fallback to timestamp).
  • Types (types/host-application-adapter.ts): Update interface for showConnectionError(conninfo?) and clarify return-to-app success doc.
• Tests:
  • Add/update cases validating error vs success toasts and that error notifications use the connection id; ensure responses without id don’t trigger return-to-app.

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

[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