question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: Could not find expected browser locally

See original GitHub issue

Bug description

I started noticing this issue as soon as I updated to v19. I didn’t change any of my code as the list of breaking changes didn’t make it seem like I had to but if that’s the issue please let me know. The issue occurs as soon as I called puppeteer.launch().

Steps to reproduce the problem:

  1. Install v19
  2. Launch a new chrome browser using puppeteer.launch({ args: ["args: ["--no-sandbox"], headless: true })
  3. Observe the error

Puppeteer version

19.0.0

Node.js version

18.10.0

npm version

Yarn 1.22.19

What operating system are you seeing the problem on?

Windows

Relevant log output

/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:69
                  throw new Error(missingText);
                        ^
  Error: Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (1045629).
      at ChromeLauncher.launch (/app/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:118:15)

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:2
  • Comments:12

github_iconTop GitHub Comments

4reactions
dmcgougancommented, Oct 21, 2022

This broke our jenkins build server

4reactions
jrandolfcommented, Oct 17, 2022

As you are using a Dockerfile, our support for setup is limited there. We ask that you use the docker image we provide as a base/inspiration since it’s tested in our CI. See pptr.dev/guides/docker. If you are already using the docker image, then you must throw out the old one and use the latest image. The older images had some permission problems, so running npm i puppeteer@latest will not resolve the issue. A full pull needs to be done.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Could not find expected browser chrome locally - Stack Overflow
Error: Could not find expected browser (chrome) locally. Run npm install to download the correct Chromium revision (884014). Tried "npm install" ...
Read more >
Could not find expected browser (chrome) locally. Run npm ...
Could not find expected browser (chrome) locally. Run npm install to download the correct Chromium revision (938248). When using serverless-esbuild plugin ...
Read more >
Puppeteer.js Error: Could not find expected browser (chrome ...
Error: Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (1022525).
Read more >
“Could not find expected browser (chrome) locally. Run `npm ...
Answers related to “Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (970485)”.
Read more >
Puppeteer on Render - Render community
im trying to run Puppeteer and im getting this error “UnhandledPromiseRejectionWarning: Error: Could not find expected browser (chrome) locally.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found