Support for macOS 11.0 Big Sur

i have been using Playwright-Sharp on macOS for while - however updating my system to macOS 11.0 Big Sur seemed to break my application with the following error:

(node:3524) UnhandledPromiseRejectionWarning: Error: ERROR: Playwright does not support chromium on mac11.0
    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:125:13)
    at Object.downloadBrowserWithProgressBar (/snapshot/playwright-cli/node_modules/playwright/lib/install/browserFetcher.js:150:17)
    at async validateCache (/snapshot/playwright-cli/node_modules/playwright/lib/install/installer.js:99:9)
    at async Object.installBrowsersWithProgressBar (/snapshot/playwright-cli/node_modules/playwright/lib/install/installer.js:56:5)
(node:3524) 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:3524) [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.

The error is caused either by Playwright.InstallAsync(); or Playwright.CreateAsync(); because it gets thrown before i can launch a browser i.e. playwright.Webkit.LaunchAsync(...).

I saw that there is the same issue in the upstream repository https://github.com/microsoft/playwright/issues/2789 so maybe it’s easy to get this into Playwright-Sharp 🤞

thank you!

[nor0x]

0.170.2 works great in my first tests. If any errors related with my previous tests occur, i will create a new issue.

Thanks @kblok !

[kblok]

The playwright cache keeps track of the directories using a browser version. If that directory is removed, and there are no more directories using that version, that browser version will be removed.

In local builds, we are using the place where the packages are stored (maybe we can improve that in the future). And that works for the main use case: UI testing.

Besides all that. You will need to call InstallAsync in your app, because your app clients won’t have the browsers installed.

i have updated my code and added await Playwright.InstallAsync() before calling Playwright.CreateAsync(), but i’m getting the same error as before

I’ll take a look