chromium version error in path

Hey Playwright creators!

I'm running into a frustrating issue with Playwright and Chromium, and I could really use some help. Here's what's going on:

The Error:

Error processing batch: 
"errorName": "BrowserLaunchError",
"errorMessage": "Failed to launch browser. Please check the following:
- Try installing the required dependencies by running `npx playwright install --with-deps` (https://playwright.dev/docs/browsers).

The original error is available in the `cause` property. Below is the error received when trying to launch a browser:

browserType.launchPersistentContext: Executable doesn't exist at /home/webapp/.cache/ms-playwright/chromium-1117/chrome-linux/chrome

Error processing batch: 
"errorName": "BrowserLaunchError",
"errorMessage": "Failed to launch browser. Please check the following:
- Try installing the required dependencies by running `npx playwright install --with-deps` (https://playwright.dev/docs/browsers).

The original error is available in the `cause` property. Below is the error received when trying to launch a browser:

browserType.launchPersistentContext: Executable doesn't exist at /home/webapp/.cache/ms-playwright/chromium-1117/chrome-linux/chrome

The Situation:

Playwright is looking for Chromium in

/home/webapp/.cache/ms-playwright/chromium-1117/chrome-linux/chrome

/home/webapp/.cache/ms-playwright/chromium-1117/chrome-linux/chrome

But I actually have Chromium installed at

/home/webapp/.cache/ms-playwright/chromium-1140/chrome-linux/chrome

/home/webapp/.cache/ms-playwright/chromium-1140/chrome-linux/chrome

My Question:
How the hell can I specify which Chromium version Playwright should use?

I don't want to specify this in ENV since I want it to work out of the box and use playwright version that it install

Any help would be greatly appreciated. I'm pulling my hair out over here!

Thanks in advance!

Hall•10/15/24, 11:10 AM

View post on community site

This post has been pushed to the community knowledgebase. Any replies in this thread will be synced to the community site.

Apify Community

ondro_k•10/15/24, 2:42 PM

Hey,

running should fix this - it will install the correct version of chrome that playwright expects.

You may also try to update your dependency, is pretty old, the latest playwright uses

GitHub

playwright/packages/playwright-core/browsers.json at main · microso...

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API. - microsoft/playwright

rubber-blueOP•10/15/24, 4:46 PM

@ondro_k I cannot run this command since I’m running it on AWS EC2 -> elasticbeanstalk which use Fedora underneath

Playwright support only Ubuntu (—with-deps will run apt command underneath - Ubuntu package manager)

Fedora (therefore Amazon Linux 2, uses yum as package manager)

I already installed in other script all packages that are installed with —with-deps flag)

ondro_k•10/15/24, 4:59 PM

aaah, I see. Can you try to run (without )? I tested it on my Fedora and it worked. It still uses ubuntu binaries but it should work fine even on Fedora:

rubber-blueOP•10/15/24, 5:03 PM

But I don’t have issue with installing chromium

I have problem that playwright is looking for directory called chromium-1117 (I develop on windows machine and npx plawright install chromium —with-deps download chromium-1117 - I guess it’s the newest version for windows)

And when I run npx playwright install chromium on Linux it will download the newest one for Linux which is chromium-1140

So this is my issue that my playwright code is looking for chromium version that is the newest on windows and not Linux

ondro_k•10/15/24, 5:38 PM

just to make sure...is your

package.json

package.json

and

package-lock.json

package-lock.json

same on both machines?

rubber-blueOP•10/15/24, 6:08 PM

Of course… why? @ondro_k

ondro_k•10/16/24, 12:28 PM

it looks like you're using different playwright versions...if you run , do you get the same versions on both machines?

ondro_k•10/16/24, 4:29 PM

I think playwrigh uses same browser version for all OSes...what I would do is to remove

node_modules

node_modules

and , then run

npm install

npm install

and then and it should install the same chromium version

rubber-blueOP•10/24/24, 6:55 AM

I figure out what was the issue - my pipelines - it was “npm I —no-package-lock” which updated node_modules and then I did npx playwright install which installed newer version and my build wanted to use the older

rubber-blueOP•10/24/24, 8:01 AM

@ondro_k what was exactly what I did the day before you answer

thank you for your help this can be marked as answer