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
Cannot spawn Chromium with custom executablePath on Apple M1 #6634
Comments
Can you please try the patch at #6495 and see if that fixes it? |
@mathiasbynens I've confirmed #6495 patch will fix the problem on Apple Silicon. Following is steps how to confirm:
Build steps (1-3) may require Intel arch. I used Linux VM provided by GitHub Codespaces to create package. It can take the screenshot via custom Chrome process even if used Apple SIlicon, like this: |
@yhatt Thanks! |
For anyone lazy coming from google, or for anyone without access to an x86 machine I have prepackaged this binary for use with a homebrew chromium install Steps:
import puppeteer from 'puppeteer-core'
async function main () {
const browser = await puppeteer.launch({
executablePath: '/Applications/Chromium.app/Contents/MacOS/Chromium',
headless: false
})
... |
Confirmed it has been fixed in the latest puppeteer-core v7!
|
@yhatt Still should pass |
@microsmsm That’s right. It has already mentioned in the documentation:
|
like a champ! |
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
Please include code that reproduces the issue.
puppeteer-core
test.js
:node ./test.js
What is the expected result?
Take a screenshot of https://example.com/ into
example.png
, with using custom executable path.What happens instead?
Puppeteer tries to spawn not existed chromium path
/usr/bin/chromium-browser
.I think Puppeteer is always overriding executable path when running on arm64. (#5167)
puppeteer/src/node/Launcher.ts
Lines 107 to 108 in 46e74ff
UPDATE: #6495 may fix it.
The text was updated successfully, but these errors were encountered: