[🐛 Bug]: metamask 11.9.1 is not compatible with ManifestV3 (latest chromium versions)

[oktapodia]

🔎 Have you searched existing issues to avoid duplicates?

• I have made sure that my issue is not a duplicate.

🧪 Have you tested your code using latest version of Synpress?

• I have made sure that my issue still exists on latest version of Synpress.

💡 Are you able to provide enough information to be able to reproduce your issue locally?

• I can provide enough details to reproduce my issue on local environment.

Synpress version

4.1.1

Node.js version

22.14.0

Operating system

Tahoe 26.1

Run mode

Playwright + Synpress (as plugin)

CI platform (if applicable)

No response

Are you running your tests inside docker? (if applicable)

• This issue could be related to docker.

What happened?

The latest version of chromium requires extensions to support ManifestV3 which is not the case >= chromium version 140

source: https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline#march_31st_2025_manifest_v2_is_disabled_with_the_option_to_re-enable_extensions

What is your expected behavior?

Upgrading the default version of metamask to the latest

How to reproduce the bug.

Simply install synpress + playwright latest version, the error will be thrown instantly

Relevant log output

Failed to load extension from: /REDACTED/.cache-synpress/metamask-chrome-11.9.1. Cannot install extension because it uses an unsupported manifest version.

[Oputo50]

I'm facing the same issue

[louis-md]

Same issue. Thank you for the great work. Impossible however to use synpress v4 (even trying with all possible combinations of playwright/cypress and phantom/metamask). The examples don't seem to work either. Sadly the repo is unusuable as is, I had to downgrade to 3.7.3, which has other issues.

EDIT: it turns out I had a misconfigured tsconfig.json. I changed module and moduleResolution properties to nodenext and it solved the issue in my case. 👍

EDIT 2: it turns out I also was running my tests on an outdated version of Chrome, when I updated the error surfaced again.

[Citoyen-du-monde]

I have the same issue.

[TheOldVar]

I’m having the same issue as well.
Has there been any progress on it?

[mikusekdan]

I have the same issue, any update?

[Citoyen-du-monde]

PR #1306 upgraded MetaMask to v13, but anyone pulling that change will find that confirmSignature() and approveTokenPermission() silently fail because they still use v11 selectors.

The problem

Synpress's confirmSignature() looks for:

.page-container__footer [data-testid="page-container-footer-next"]

This selector does not exist in MetaMask v13. The v13 UI uses [data-testid="confirm-btn"] for transaction approvals, spending cap requests, and signature confirmations.

Solution

We wrote a drop-in replacement for confirmSignature() that supports v13's selectors with v11 fallback:

const CONFIRM_BUTTON_SELECTORS = [
  '[data-testid="confirm-btn"]',                // v13 primary
  '[data-testid="page-container-footer-next"]',  // v11 fallback
  '[data-testid="connect-approve"]',
  'button:has-text("Confirm")',
  'button:has-text("Connect")',
  'button:has-text("Next")',
]

const findApprovalPage = async (metamask: MetaMask, timeout = 15_000) => {
  const extensionPrefix = `chrome-extension://${metamask.extensionId}/`
  const isApprovalUrl = (url: string) =>
    url.startsWith(extensionPrefix) &&
    (url.includes('notification.html') ||
     url.includes('sidepanel.html#connect') ||
     url.includes('popup.html#connect'))

  const startedAt = Date.now()
  while (Date.now() - startedAt < timeout) {
    const page = metamask.context.pages().find((p) => isApprovalUrl(p.url()))
    if (page) return page
    await new Promise((r) => setTimeout(r, 500))
  }
  return null
}

const waitForConfirmButton = async (approvalPage: Page, timeout = 25_000) => {
  const startedAt = Date.now()
  while (Date.now() - startedAt < timeout) {
    // Handle MV3 re-locking mid-flow
    const passwordInput = approvalPage.getByTestId('unlock-password')
    if (await passwordInput.isVisible({ timeout: 1000 }).catch(() => false)) {
      await passwordInput.fill(process.env.WALLET_PASSWORD!)
      await approvalPage.getByTestId('unlock-submit').click()
      await new Promise((r) => setTimeout(r, 2000))
      continue
    }

    for (const selector of CONFIRM_BUTTON_SELECTORS) {
      const button = approvalPage.locator(selector).first()
      if (await button.isVisible({ timeout: 500 }).catch(() => false)) {
        return button
      }
    }
    await new Promise((r) => setTimeout(r, 500))
  }
  return null
}

export const confirmTransaction = async (
  metamask: MetaMask,
  timeout = 30_000
): Promise<boolean> => {
  const approvalPage = await findApprovalPage(metamask, timeout)

  if (!approvalPage) {
    // No popup — transaction may have been auto-confirmed
    return false
  }

  await approvalPage.bringToFront()
  const confirmButton = await waitForConfirmButton(approvalPage, 25_000)

  if (!confirmButton) return false

  await confirmButton.click()
  await new Promise((r) => setTimeout(r, 1500))

  // Handle multi-step flows (e.g. spending cap → deposit)
  if (!approvalPage.isClosed()) {
    const secondButton = await waitForConfirmButton(approvalPage, 5000)
    if (secondButton) await secondButton.click()
  }

  return true
}

Important MV3 quirk: MetaMask v13 can re-lock itself inside the notification popup when the service worker goes idle. The waitForConfirmButton function checks for the lock screen before looking for buttons — without this, tests will hang on the lock screen forever.