feat: Solana accountChanged event

[jiexi]

Description

• Adds solana accountChange support
• Fixes issue with selecting non-evm account from dapp account switcher

Related issues

Fixes:

Manual testing steps

1. yarn setup
2. yarn start:ios:flask
3. Launch flask build
4. Make two solana accounts
5. Go to any webpage with in app browser
6. Enter the block of code below in the Safari dev console for the webpage (Open safari on your computer, Click Develop, Select the metamask app browser tab running in the simulator. You have to enable safari dev mode first)
7. Permit 2 solana accounts and 1 eth account (the eth account is needed so that you can get back into modifying the permissions since there is a bug with the selectors right now)
8. Play around

window.addEventListener('message', (event) => {
  const {
    target,
    data
  } = event.data;
  if (
    target !== "metamask-inpage" ||
    data?.name !== 'metamask-multichain-provider'
  ) {
    return;
  }
  console.log(data.data)
})

const caipPostMessage = (data) => {
  window.postMessage({
    target: 'metamask-contentscript',
    data: {
      name: 'metamask-multichain-provider',
      data
    }
  }, location.origin)
}

caipPostMessage({
    jsonrpc: "2.0",
    method: "wallet_createSession",
    params: {
      optionalScopes: {
        "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp": {
          methods: [],
          notifications: [],
          accounts: [],
        },
      },
      sessionProperties: {
        solana_accountChanged_notifications: true,
      },
    },
  })

Screenshots/Recordings

Before

After

Screen.Recording.2025-05-22.at.2.54.56.PM.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.

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

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 8dd30f4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3ad12d6e-4df4-4d55-be2c-c90e8e825f7e

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

[adonesky1]

Tested/validated latest and all functionality is looking great!

[adonesky1]

LGTM. Just small non blocking nits

[sonarqubecloud]

Quality Gate failed

Failed conditions
75.4% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[sethkfman]

LGTM. Reviewed the browser changes for the platform

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 65513d4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3b9087f8-955a-44e8-a8c0-7c0e199b1328

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