-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Bug]: Error: Could not find Chromium (rev. 1069273) #9533
Comments
How did you upgrade Puppeteer? binary installation happens in the |
As a workaround it should be possible to run |
Hello, is there any solution for this problem? |
I could not reproduce the issue but I think I found a related issue that might explain the missing binaries. |
Since we moved to the central binaries cache it does not make sense to clean up old binaries automatically because multiple installations can use different versions. We expect the users to clean the cache from time to time until we offer a CLI for managing the browsers. Closes #9533
Since we moved to the central binaries cache it does not make sense to clean up old binaries automatically because multiple installations can use different versions. We expect the users to clean the cache from time to time until we offer a CLI for managing the browsers. Closes #9533
Very random but persistent issue. It seems not reproducible if you run a single script with no concurrency. Try with concurrency and long running scripts like in a real world scenario. When it breaks (and it breaks during script execution), it is not recoverable until a new npm ci. And then, it can breaks after 26 minutes or after 3 minutes, but when it breaks it will not recover even if you re-run the same script. |
Since we moved to the central binaries cache it does not make sense to clean up old binaries automatically because multiple installations can use different versions. We expect the users to clean the cache from time to time until we offer a CLI for managing the browsers. Closes #9533
BTW @smithkyle solution works also with 1st gen functions... |
This one worked for me, thanks! |
SOLVED (debian linux 12) Please add in script to print the expected path that puppeeter is searching chromium. note that running as sudo yarn PROGRAM is searching in root/.cache while yarn PROGRAM in /home/user... So, |
In a Windows environment, a global installation of Puppeteer solved the problem:
|
Yep, that worked for me, thank you! |
Error: Could not find Chrome (ver. 119.0.6045.105). This can occur if either
|
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
It seems that Chromium is no longer found automatically. See also puppeteer/puppeteer#9533.
mermaid-filter depends on a deprecated version of puppeteer, which results in puppeteer no longer finding a suitable version of Chromium. See puppeteer/puppeteer#9533 for others facing this issue. Forcing npm to use the most recent release of puppeteer (version 21) resolves this problem. We should revert the workflow to one that doesn't text-insert a dependency and just directly npm installs mermaid-filter once mermaid-js/mermaid-cli#627 has been resolved, a new release of mermaid-cli been produced, and mermaid-filter having picked up that new release.
I'm still experiencing this issue despite trying all the workarounds. My issue specifically is that we can't get this to work in an AWS lambda. |
you can install puppeteer : then You can manually download Chromium (e.g. via this page or this page) and then set the executablePath when launching it: const browser = await puppeteer.launch({ |
Bug expectation
I expected to successfully run puppeteer, as it always did in prior versions.
I instead got an error:
Error: Could not find Chromium (rev. 1069273). This can occur if either
npm install
) orFor (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
at ChromeLauncher.resolveExecutablePath (/var/www/html/oas-restapi-fork1/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:119:27)
at ChromeLauncher.executablePath (/var/www/html/oas-restapi-fork1/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:205:25)
at ChromeLauncher.launch (/var/www/html/oas-restapi-fork1/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:93:37)
Bug behavior
Minimal, reproducible example
Error string
Error: Could not find Chromium (rev. 1069273)
Puppeteer configuration
Puppeteer version
19.6.0
Node version
v16.19.0
Package manager
npm
Package manager version
9.3.0
Operating system
Linux
The text was updated successfully, but these errors were encountered: