Fix mmc release v31 (#2876)

* Docs: Add CSP QR-code troubleshooting

Add a new troubleshooting 'Cause C' that explains how a strict Content Security Policy can prevent the MetaMask QR code from rendering (the fox SVG is embedded as a data: URI and materialized via a fetch-style call). The entry documents the console error, outlines the required CSP directives (allow data: in connect-src/img-src, include mm-sdk relay and analytics origins, and style-src 'unsafe-inline'), provides a minimal meta-tag example, and links to the connect-monorepo CSP reference.

* Apply suggestion from @alexandratran

* Update EVM docs for connectAndSign/connectWith API

Document breaking API changes: connectAndSign and connectWith now return objects ({ accounts, chainId, signature }) and ({ accounts, chainId, result }) respectively. Updated examples across quickstart, guides, and reference to destructure these fields and log accounts/chainId alongside results, and added breaking-change notes. Also adjusted the EVM client status type name to ConnectEvmStatus in the reference and clarified CSP troubleshooting guidance for the QR-code fox SVG (img-src data: and older-version fallbacks).

* Clarify connectAndSign/connectWith return docs

Update wording in EVM guides and reference to clarify that connectAndSign and connectWith now return objects and callers should read `.signature` and `.result` from the returned object (rather than implying destructuring). Minor punctuation/phrasing tweaks in migrate-from-sdk guide and methods reference for clearer guidance.

* Update linea bridge link

---------

Co-authored-by: Alexandra Carrillo <12214231+alexandratran@users.noreply.github.com>

Author: shahbaz17

metamask-connect/evm/guides/manage-user-accounts.md

@@ -217,8 +217,10 @@ const evmClient = await createEVMClient({
 
 async function handleConnectAndSign() {
   try {
-    const signature = await evmClient.connectAndSign({ message: 'Hello in one go!' })
-    console.log('Signature:', signature)
+    const { accounts, chainId, signature } = await evmClient.connectAndSign({
+      message: 'Hello in one go!',
+    })
+    console.log('Accounts:', accounts, 'Chain:', chainId, 'Signature:', signature)
   } catch (err) {
     console.error('Error with connectAndSign:', err)
   }

metamask-connect/evm/guides/migrate-from-sdk.md

@@ -191,28 +191,42 @@ Chain IDs must be hex strings. Use `'0x1'`, not `1` or `'1'`, in `chainIds` and
 #### Connect-and-sign shortcut
 
 Use `connectAndSign` to connect and sign a `personal_sign` message in one user approval.
-The method returns the signature directly:
+The method returns `{ accounts, chainId, signature }`:
 
 ```typescript
-const signature = await client.connectAndSign({
+const { accounts, chainId, signature } = await client.connectAndSign({
   message: 'Sign in to My Dapp',
   chainIds: ['0x1'],
 })
 ```
 
+:::info Breaking change in `@metamask/connect-evm` 1.0.0
+`connectAndSign` previously returned the signature as a bare string. It now returns an object,
+so read `.signature` from the returned object to get the signed value.
+:::
+
 #### Connect-and-execute shortcut
 
 Connect and execute any JSON-RPC method in a single user approval.
-The method returns the RPC result directly:
+The method returns `{ accounts, chainId, result }`:
 
 ```typescript
-const txHash = await client.connectWith({
+const {
+  accounts,
+  chainId,
+  result: txHash,
+} = await client.connectWith({
   method: 'eth_sendTransaction',
   params: account => [{ from: account, to: '0x...', value: '0x0' }],
   chainIds: ['0x1'],
 })
 ```
 
+:::info Breaking change in `@metamask/connect-evm` 1.0.0
+`connectWith` previously returned the raw RPC result. It now returns an object,
+so read `.result` from the returned object to get the RPC response value.
+:::
+
 :::tip React Native polyfills
 Browser-based setups (Vite, Webpack) work without polyfills. If you are migrating a **React Native**
 app and encounter errors referencing `Buffer`, `crypto`, `stream`, or `Event is not defined`, see

metamask-connect/evm/quickstart/javascript.md

@@ -217,7 +217,7 @@ Use [`provider.request`](../reference/provider-api.md#request) for arbitrary [JS
 const { accounts, chainId } = await evmClient.connect()
 
 // 2. Connect and sign in one step
-const signature = await evmClient.connectAndSign({
+const { signature } = await evmClient.connectAndSign({
   message: 'Sign in to the dapp',
 })
 

metamask-connect/evm/reference/methods.md

@@ -67,16 +67,27 @@ Connects to MetaMask and signs a `personal_sign` message in a single user approv
 
 ### Returns
 
-A promise that resolves to the signature as a hex string.
+A promise that resolves to an object with the following fields:
+
+| Field       | Type        | Description                                      |
+| ----------- | ----------- | ------------------------------------------------ |
+| `accounts`  | `Address[]` | The accounts permitted on the resulting session. |
+| `chainId`   | `Hex`       | The selected chain ID as a hex string.           |
+| `signature` | `string`    | The `personal_sign` signature as a hex string.   |
+
+:::info Breaking change in `@metamask/connect-evm` 1.0.0
+`connectAndSign` previously returned the signature as a bare string. It now returns
+`{ accounts, chainId, signature }`. Read `.signature` from the returned object to get the signed value.
+:::
 
 :::tip
-To access the connected accounts and chain ID alongside the signature, use the `connectAndSign` event handler
-when [initializing the client](../quickstart/javascript.md):
+You can also subscribe to the `connectAndSign` event handler
+when [initializing the client](../quickstart/javascript.md) to receive the same payload:
 
 ```javascript
 eventHandlers: {
-  connectAndSign: ({ accounts, chainId, signResponse }) => {
-    console.log('Accounts:', accounts, 'Chain:', chainId, 'Signature:', signResponse)
+  connectAndSign: ({ accounts, chainId, signature }) => {
+    console.log('Accounts:', accounts, 'Chain:', chainId, 'Signature:', signature)
   },
 }
 ```
@@ -86,11 +97,11 @@ eventHandlers: {
 ### Example
 
 ```javascript
-const signature = await evmClient.connectAndSign({
+const { accounts, chainId, signature } = await evmClient.connectAndSign({
   message: 'Sign in to My Dapp',
   chainIds: ['0x1'],
 })
-console.log('Signature:', signature)
+console.log('Accounts:', accounts, 'Chain:', chainId, 'Signature:', signature)
 ```
 
 ## `connectWith`
@@ -109,16 +120,27 @@ Connects to MetaMask and executes a specific [JSON-RPC method](json-rpc-api/inde
 
 ### Returns
 
-A promise that resolves to the result of the RPC method invocation.
+A promise that resolves to an object with the following fields:
+
+| Field      | Type        | Description                                      |
+| ---------- | ----------- | ------------------------------------------------ |
+| `accounts` | `Address[]` | The accounts permitted on the resulting session. |
+| `chainId`  | `Hex`       | The selected chain ID as a hex string.           |
+| `result`   | `unknown`   | The result of the JSON-RPC method invocation.    |
+
+:::info Breaking change in `@metamask/connect-evm` 1.0.0
+`connectWith` previously returned the raw RPC result. It now returns
+`{ accounts, chainId, result }`. Read `.result` from the returned object to get the RPC response value.
+:::
 
 :::tip
-To access the connected accounts and chain ID alongside the result, use the `connectWith` event handler
-when [initializing the client](../quickstart/javascript.md):
+You can also subscribe to the `connectWith` event handler
+when [initializing the client](../quickstart/javascript.md) to receive the same payload:
 
 ```javascript
 eventHandlers: {
-  connectWith: ({ accounts, chainId, connectWithResponse }) => {
-    console.log('Accounts:', accounts, 'Chain:', chainId, 'Result:', connectWithResponse)
+  connectWith: ({ accounts, chainId, result }) => {
+    console.log('Accounts:', accounts, 'Chain:', chainId, 'Result:', result)
   },
 }
 ```
@@ -128,7 +150,11 @@ eventHandlers: {
 ### Example
 
 ```javascript
-const txHash = await evmClient.connectWith({
+const {
+  accounts,
+  chainId,
+  result: txHash,
+} = await evmClient.connectWith({
   method: 'eth_sendTransaction',
   params: account => [
     {
@@ -139,7 +165,7 @@ const txHash = await evmClient.connectWith({
   ],
   chainIds: ['0x1'],
 })
-console.log('Transaction hash:', txHash)
+console.log('Accounts:', accounts, 'Chain:', chainId, 'Transaction hash:', txHash)
 ```
 
 ## `switchChain`
@@ -283,7 +309,7 @@ The EVM client exposes the following read-only properties:
 | `accounts`        | `Address[]`            | Currently permitted accounts.                                                                   |
 | `selectedAccount` | `Address \| undefined` | Currently selected account (first in `accounts`).                                               |
 | `selectedChainId` | `Hex \| undefined`     | Currently selected chain ID as a hex string.                                                    |
-| `status`          | `ConnectionStatus`     | Connection status: `'loaded'`, `'pending'`, `'connecting'`, `'connected'`, or `'disconnected'`. |
+| `status`          | `ConnectEvmStatus`     | Connection status: `'loaded'`, `'pending'`, `'connecting'`, `'connected'`, or `'disconnected'`. |
 
 ### Example
 

metamask-connect/troubleshooting/index.md

@@ -174,34 +174,43 @@ const client = await createEVMClient({
 ```
 
 **Cause C:** A strict Content Security Policy (CSP) is blocking the QR code from rendering.
-The QR code embeds the MetaMask fox SVG as a `data:` URI, which `@metamask/multichain-ui`
-materializes via a `fetch`-style call.
-A CSP without `data:` in `connect-src` (or `img-src`) blocks this and the QR code fails to appear.
-A symptom in the browser console looks like:
+The QR code embeds the MetaMask fox SVG as a `data:` URI.
 
-`Refused to connect to 'data:image/svg+xml;base64,...' because it violates the following Content Security Policy directive: "connect-src 'self' https: wss:".`
-
-**Fix:** Allow the `data:` scheme and the MetaMask relay and analytics origins in your CSP.
+**Fix:** Allow the `data:` scheme in `img-src` and the MetaMask relay and analytics origins in
+`connect-src`.
 A minimal working policy looks like:
 
 ```html
 <meta
   http-equiv="Content-Security-Policy"
   content="
-    connect-src 'self' data: https://*.infura.io wss://mm-sdk-relay.api.cx.metamask.io https://mm-sdk-analytics.api.cx.metamask.io;
+    connect-src 'self' https://*.infura.io wss://mm-sdk-relay.api.cx.metamask.io https://mm-sdk-analytics.api.cx.metamask.io;
     img-src 'self' data:;
     style-src 'self' 'unsafe-inline';
   " />
 ```
 
-- `data:` in `connect-src` and `img-src` - Required for the fox SVG embedded in the QR code.
+- `img-src 'self' data:` - Required for the fox SVG embedded in the QR code.
 - `wss://mm-sdk-relay.api.cx.metamask.io` - The relay used for remote (no-extension and mobile)
   connections.
 - `https://mm-sdk-analytics.api.cx.metamask.io` - The default analytics endpoint emitted during the
   connection lifecycle.
 - `style-src 'unsafe-inline'` - `@metamask/multichain-ui` injects component styles at runtime
   inside Shadow DOM (Stencil).
 
+:::note Older versions
+In earlier package versions, the QR-code modal materialized the fox icon via an `XMLHttpRequest` on
+a `blob:` / `data:` URI, requiring `blob:` (and in some setups `data:`) in `connect-src`.
+Upgrade to `@metamask/connect-evm` 1.0.0, `@metamask/connect-solana` 1.0.0, or
+`@metamask/connect-multichain` 0.12.1 or later to remove this requirement — the fox SVG is now
+embedded directly as a `data:` URI without an extra request.
+A symptom on older versions looked like:
+
+`Refused to connect to 'data:image/svg+xml;base64,...' because it violates the following Content Security Policy directive: "connect-src 'self' https: wss:".`
+
+If you cannot upgrade, add `data: blob:` to `connect-src` as a fallback.
+:::
+
 For the full reference, see
 [Content Security Policy](https://github.com/MetaMask/connect-monorepo#content-security-policy) in `metamask/connect-monorepo`.
 

services/how-to/get-testnet-tokens.md

@@ -23,7 +23,7 @@ Use [testnet endpoints](../get-started/endpoints.md) during development and init
 | [Binance Smart Chain (BSC) Sepolia](https://academy.binance.com/en/articles/connecting-metamask-to-binance-smart-chain)     | [BSC Sepolia faucet](https://www.bnbchain.org/en/testnet-faucet)                         | [BSC bridge](https://www.bnbchain.org/en/bnb-chain-bridge)         |
 | [Celo Sepolia](https://docs.celo.org/build-on-celo/network-overview)                                                        | [Celo Sepolia faucet](https://faucet.celo.org/celo-sepolia)                              | [Celo bridge](https://docs.celo.org/protocol/bridge#token-bridges) |
 | [Ethereum Sepolia](https://ethereum.org/developers/docs/networks/)                                                          | [Ethereum Sepolia faucet](https://faucet.quicknode.com/ethereum/sepolia)                 | [Sepolia bridge](https://docs.blast.io/building/bridges/testnet)   |
-| [Linea Sepolia](https://support.linea.build/getting-started/how-to-get-linea-goerli-testnet-eth)                            | [Linea Sepolia faucet](https://docs.metamask.io/developer-tools/faucet)                  | [Linea bridge](https://bridge.linea.build)                         |
+| [Linea Sepolia](https://support.linea.build/getting-started/how-to-get-linea-goerli-testnet-eth)                            | [Linea Sepolia faucet](https://docs.metamask.io/developer-tools/faucet)                  | [Linea bridge](https://linea.build/hub/bridge)                     |
 | [Mantle Sepolia](https://docs.mantle.xyz/network/for-uers/how-to-guides/connecting-wallet-to-mantle-network)                | [Mantle Sepolia faucet](https://faucet.sepolia.mantle.xyz)                               | [Mantle bridge](https://app.mantle.xyz/bridge?network=sepolia)     |
 | [Optimism Sepolia](https://docs.optimism.io/app-developers/tools/faucets)                                                   | [Optimism Sepolia faucet](https://faucet.quicknode.com/optimism/sepolia)                 | [Optimism bridge](https://app.optimism.io/bridge)                  |
 | [Polygon Amoy](https://docs.polygon.technology/tools/wallets/metamask/add-polygon-network/)                                 | [Polygon Amoy faucet](https://faucet.polygon.technology)                                 | [Polygon bridge](https://portal.polygon.technology/bridge)         |