chore: update the 'sendMessage' method in the 'DeeplinkProtocolService' class

[omridan159]

Description

Updated the sendMessage method in the DeeplinkProtocolService class.

Changes Made:

• Attached chainId and selectedAccounts to each sent message.

Code Snippet:

async sendMessage(message: any, forceRedirect?: boolean) {
  const messageWithMetadata = {
    ...message,
    data: {
      ...message.data,
      chainId: this.getChainId(),
      accounts: this.getSelectedAccounts(),
    },
  };
  // rest of the method implementation
}

This PR addresses several key issues and enhancements:

1. Account Screen Hang Fix:

• Resolved an issue where the account screen would hang due to a chain mismatch. Now, users will either be switched automatically or prompted to switch chains, ensuring a smooth user experience.

2. Chain Switching Improvement:

• Enhanced the handling of chain switching. Users can now switch chains in MetaMask without unnecessary alerts or state preservation issues. This allows for a more seamless interaction with Warpcast.

3. Batch Request Handling:

• Fixed the problem where batch requests were returning empty arrays. The system now correctly handles batch requests with methods like wallet_switchEthereumChain.

4. Deeplink Protocol Service Updates:

• Updated the sendMessage method to include chainId and selected accounts in the message metadata. This ensures that all messages carry the necessary information for accurate processing.
• Improved the handling of multichain RPC call responses, ensuring that batch RPC responses are managed correctly and users are redirected appropriately if an error occurs.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

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.

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.

[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.

[andreahaku]

LGTM

[elefantel]

Looks good

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[christopherferreira9]

Good for iOS and Android using the ReactNative SDK.

Test cases

GIVEN that a user has a ReactNative SDK dapp installed on iOS
WHEN the user changes the chain on the wallet side after connecting
AND the user tries to sign
THEN the user should get a message warning that chains are out of sync

GIVEN that a user has a ReactNative SDK dapp installed on Android
AND the user tries to sign
WHEN the user changes the chain on the wallet side after connecting
THEN the suer should be prompt to sign

GIVEN that a user has a ReactNative SDK dapp installed on iOS
WHEN the user tris to perform batch with: switchChain + sign
THEN the response should not contain the null in the first response

A the time of testing this PR for android it still returns [null, 0x00..] but it is fixed for ios where the response looks like [0x00..]

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 3dadfe4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/65cb9d88-2165-4b18-8a1d-b07c816e5fd4

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[elefantel]

Looks good