Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Playwright does not support chromium on mac11.1 #4775

Closed
mer163 opened this issue Dec 19, 2020 · 14 comments · Fixed by #5016
Closed

[Feature] Playwright does not support chromium on mac11.1 #4775

mer163 opened this issue Dec 19, 2020 · 14 comments · Fixed by #5016
Assignees

Comments

@mer163
Copy link

mer163 commented Dec 19, 2020

(node:1278) UnhandledPromiseRejectionWarning: Error: ERROR: Playwright does not support chromium on mac11.1

@aslushnikov
Copy link
Collaborator

Which playwright version did you try? Playwright v1.7.0 should support it just fine.

@xg-wang
Copy link
Contributor

xg-wang commented Dec 23, 2020

I'm on playwright 1.6.2 and seeing this error.

I was running node node_modules/playwright/install.js to be able to see the error message, normal yarn install succeeds but left ~/Library/Caches/ms-playwright empty folder. I would expect playwright to throw a better error. Also, why is mac11.1 not supported?

❯ node node_modules/playwright/install.js
(node:21410) UnhandledPromiseRejectionWarning: Error: ERROR: Playwright does not support chromium on mac11.1
    at Object.assert (node_modules/playwright/lib/utils/utils.js:58:15)
    at revisionURL (node_modules/playwright/lib/install/browserFetcher.js:131:13)
    at Object.downloadBrowserWithProgressBar (node_modules/playwright/lib/install/browserFetcher.js:156:17)
    at async validateCache (node_modules/playwright/lib/install/installer.js:99:9)
    at async installBrowsersWithProgressBar (node_modules/playwright/lib/install/installer.js:56:5)

Upgrading to 1.7.0 does fix the issue.

@nwittwer
Copy link

nwittwer commented Dec 30, 2020

Seeing this error also on MacOS 11.2 (beta) with Playwright 1.7.1. I'm only seeing this error when trying to use PLAYWRIGHT_BROWSERS_PATH=0.

npm i playwright -D
> [email protected] install /Users/me/node_modules/playwright
> node install.js
(node:16194) UnhandledPromiseRejectionWarning: Error: ERROR: Playwright does not support chromium on mac11.2
    at Object.assert (/Users/me/Desktop/playwright-test/node_modules/playwright/lib/utils/utils.js:58:15)
    at revisionURL (/Users/me/Desktop/playwright-test/node_modules/playwright/lib/install/browserFetcher.js:143:13)
    at Object.downloadBrowserWithProgressBar (/Users/me/Desktop/playwright-test/node_modules/playwright/lib/install/browserFetcher.js:168:17)
    at async validateCache (/Users/me/Desktop/playwright-test/node_modules/playwright/lib/install/installer.js:103:9)
    at async installBrowsersWithProgressBar (/Users/me/Desktop/playwright-test/node_modules/playwright/lib/install/installer.js:60:5)
  1. It works on a fresh install using npm install and Playwright ^1.7.1 as a dev dependency
  2. Running npm i playwright -D also works
  3. Running PLAYWRIGHT_BROWSERS_PATH=0 npm i playwright does NOT work on MacOS 11.2 (beta). I specifically used the command npx cross-env PLAYWRIGHT_BROWSERS_PATH=0 npm i playwright, but it should be the same.

@aslushnikov aslushnikov self-assigned this Dec 31, 2020
@MarcoZehe
Copy link

I am seeing this error, too, when trying to build VsCode. Pulling current Master, making sure all build prerequisites are met, then running yarn results in this error:

error /Users/marco/projects/vscode/node_modules/playwright: Command failed.
Exit code: 1
Command: node install.js
Arguments: 
Directory: /Users/marco/projects/vscode/node_modules/playwright
Output:
/Users/marco/projects/vscode/node_modules/playwright/lib/utils/utils.js:58
        throw new Error(message);
              ^

Error: ERROR: Playwright does not support chromium on mac11.2-arm64
    at Object.assert (/Users/marco/projects/vscode/node_modules/playwright/lib/utils/utils.js:58:15)
    at revisionURL (/Users/marco/projects/vscode/node_modules/playwright/lib/install/browserFetcher.js:143:13)
    at Object.downloadBrowserWithProgressBar (/Users/marco/projects/vscode/node_modules/playwright/lib/install/browserFetcher.js:168:17)
    at async validateCache (/Users/marco/projects/vscode/node_modules/playwright/lib/install/installer.js:103:9)

This is on an M1 MacBook Pro running the 11.2 Beta. VSCode Insiders itself runs perfectly fine natively on this machine.

aslushnikov added a commit to aslushnikov/playwright that referenced this issue Jan 14, 2021
Pre-BigSur, MacOS updates were labeled as "minor" releases, so we had
to bake separate builds for different 10.X releases.

In BigSur era, it doesn't seem to be the case, so for now we can re-use
our BigSur builds across all BigSur versions (11.0, 11.1 and 11.2).

If we ever need to have a custom build for some bigsur minor version,
e.g. `11.6`, we'll have a new browser platform along with generic
`mac11` platform.

Fixes microsoft#4775.
aslushnikov added a commit that referenced this issue Jan 14, 2021
Pre-BigSur, MacOS updates were labeled as "minor" releases, so we had
to bake separate builds for different 10.X releases.

In BigSur era, it doesn't seem to be the case, so for now we can re-use
our BigSur builds across all BigSur versions (11.0, 11.1 and 11.2).

If we ever need to have a custom build for some bigsur minor version,
e.g. `11.6`, we'll have a new browser platform along with generic
`mac11` platform.

Fixes #4775.
@karoukastro
Copy link

Hi @aslushnikov I installed it today and it is returning error. What should I do?

carol@Carolinas-MBP parodify % python3 -m playwright install
Failed to process descriptor at /Users/carol/robot/parodify/node_modules/playwright
Removing unused browser at /Users/carol/Library/Caches/ms-playwright/chromium-844399
Removing unused browser at /Users/carol/Library/Caches/ms-playwright/firefox-1225
Removing unused browser at /Users/carol/Library/Caches/ms-playwright/webkit-1423
(node:3565) UnhandledPromiseRejectionWarning: Error: ERROR: Playwright does not support chromium on mac11.2
at Object.assert (/snapshot/playwright-cli/node_modules/playwright/lib/utils/utils.js:58:15)
at revisionURL (/snapshot/playwright-cli/node_modules/playwright/lib/install/browserFetcher.js:143:13)
at Object.downloadBrowserWithProgressBar (/snapshot/playwright-cli/node_modules/playwright/lib/install/browserFetcher.js:168:17)
at async validateCache (/snapshot/playwright-cli/node_modules/playwright/lib/install/installer.js:103:9)
at async Object.installBrowsersWithProgressBar (/snapshot/playwright-cli/node_modules/playwright/lib/install/installer.js:60:5)
(node:3565) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:3565) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@aslushnikov
Copy link
Collaborator

@karoukastro which version of playwright-python do you use? The bugfix should be available in version 1.8.0 and is not available in earlier versions on playwright-python.

@karoukastro
Copy link

@aslushnikov Playwright Version: 1.8.1
I've raised a new bug: #5443

@JayKishoreDuvvuri
Copy link

Yes the Bug still exists. I can still see this error Playwright does not support chromium for MacOs 11.2

@juli1
Copy link

juli1 commented Apr 28, 2021

I still have the issue when trying to install playright with npm.

pip3 install playwright==1.9.0

and then

$ npm i
npm ERR! code 1
npm ERR! path /Users/julien/git/ci-react-frontend/node_modules/playwright
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! /Users/julien/git/ci-react-frontend/node_modules/playwright/lib/utils/utils.js:58
npm ERR!         throw new Error(message);
npm ERR!               ^
npm ERR!
npm ERR! Error: ERROR: Playwright does not support chromium on mac11.2
npm ERR!     at Object.assert (/Users/julien/git/ci-react-frontend/node_modules/playwright/lib/utils/utils.js:58:15)
npm ERR!     at revisionURL (/Users/julien/git/ci-react-frontend/node_modules/playwright/lib/install/browserFetcher.js:143:13)
npm ERR!     at Object.downloadBrowserWithProgressBar (/Users/julien/git/ci-react-frontend/node_modules/playwright/lib/install/browserFetcher.js:168:17)
npm ERR!     at async validateCache (/Users/julien/git/ci-react-frontend/node_modules/playwright/lib/install/installer.js:103:9)
npm ERR!     at async installBrowsersWithProgressBar (/Users/julien/git/ci-react-frontend/node_modules/playwright/lib/install/installer.js:60:5)

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/julien/.npm/_logs/2021-04-28T16_48_08_543Z-debug.log

@mxschmitt
Copy link
Member

mxschmitt commented Apr 29, 2021

@juli1 is it also reproducible on Playwright 1.10? pip3 install playwright==1.12.1

@JayKishoreDuvvuri
Copy link

I still see the error on MacOS Big Sur 11.2 saying playwright does not support chromium

@JayKishoreDuvvuri
Copy link

JayKishoreDuvvuri commented Jul 7, 2021 via email

@WaliHassanKhan
Copy link

WaliHassanKhan commented Dec 14, 2021

tried to run yarn on a nodejs package and the problem still exists.

/node_modules/playwright-core/lib/helper.js:311
throw new Error(message);
^

Error: Unsupported platform for chromium: mac11.2

@mxschmitt
Copy link
Member

mxschmitt commented Dec 14, 2021

Please open a new issue, with more details since its fixed in a recent Playwright version.


Locking this issue - to not spam the other subscribed folks.

@microsoft microsoft locked and limited conversation to collaborators Dec 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants