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

“Could not find Chrome”—Broken by latest spec-prod update? #185

Closed
frivoal opened this issue May 29, 2024 · 4 comments · Fixed by #186
Closed

“Could not find Chrome”—Broken by latest spec-prod update? #185

frivoal opened this issue May 29, 2024 · 4 comments · Fixed by #186
Labels
bug Something isn't working

Comments

@frivoal
Copy link

frivoal commented May 29, 2024

Things used to work, but now they don't:

Compare:

There was no change on my side. I suspect the culprit is 60b3790

@sidvishnoi sidvishnoi added the bug Something isn't working label May 29, 2024
@frivoal
Copy link
Author

frivoal commented May 29, 2024

Or maybe it's something else? Seems similar to #179

@sidvishnoi
Copy link
Member

I think I should stop using PUPPETEER_EXECUTABLE_PATH env var altogether (We try to existing google-chrome executable where possible). It'll cause a performance hit, but at least it won't break. Will investigate further..

@sidvishnoi
Copy link
Member

@frivoal Should be fine now.

@frivoal
Copy link
Author

frivoal commented May 29, 2024

Thanks, that worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants