ExecutablePath option ignored

[nc]

MacOS / BigSur
Node 16 (Head)
puppeteer-core, 5.5.0

const puppeteer = require('puppeteer-core');
const browser = await puppeteer.launch({
  product: 'chrome',
  headless: false,
  executablePath: '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'
});

Fails with

Error: Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT

As I understand it, it should not be trying to launch chromium at all given the above options and use of puppeteer-core.

[nc]

If however, one modifies the BrowserRunner directly to hardcode the executablePath as shown above, all works as expected. So it seems to be an issue with how the option is being passed to Puppeteer, or how it's being handled.

class BrowserRunner {
    constructor(executablePath, processArguments, tempDirectory) {
        this.proc = null;
        this.connection = null;
        this._closed = true;
        this._listeners = [];
        this._executablePath = executablePath;
        this._processArguments = processArguments;
        this._tempDirectory = tempDirectory;
    }
    start(options) {
        console.log('>>>>', this._executablePath);
        this._executablePath = '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome';

This prints
>>>> /usr/bin/chromium-browser
and then proceeds to launch Google Chrome as expected.

[eugene1g]

This happens on Apple Silicon. The path is hardcoded at

puppeteer/src/node/Launcher.ts

Lines 106 to 109 in d901696

	let chromeExecutable = executablePath;
	if (os.arch() === 'arm64') {
	chromeExecutable = '/usr/bin/chromium-browser';
	} else if (!executablePath) {

introduced in 354f942

Chromium can run natively on Apple Silicon. Puppeteer does not yet link to that binary, but if the developer uses executablePath to point to another Chrome instance (that might not be compatible with Puppeteer), they already take on those risks and the library should just accept that path.

[eugene1g]

Related #6641 #6495 #6634

[PrzemekCh]

If however, one modifies the BrowserRunner directly to hardcode the executablePath as shown above, all works as expected. So it seems to be an issue with how the option is being passed to Puppeteer, or how it's being handled.

class BrowserRunner {
    constructor(executablePath, processArguments, tempDirectory) {
        this.proc = null;
        this.connection = null;
        this._closed = true;
        this._listeners = [];
        this._executablePath = executablePath;
        this._processArguments = processArguments;
        this._tempDirectory = tempDirectory;
    }
    start(options) {
        console.log('>>>>', this._executablePath);
        this._executablePath = '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome';

This prints
>>>> /usr/bin/chromium-browser
and then proceeds to launch Google Chrome as expected.

You saved my day :)

[thamwangjun]

I think this is a duplicate of #6634, and this issue has been fixed in this merge request #6495.
In the latest puppeteer version 10.4.0, executablePath is working in my tests.

[stale]

We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days.

[stale]

We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!

[behemoth-thainv]

I'm using puppeteer-core@^5.2.1.
Here is solution if you won't update version:

Get chronium path on your device:

which chromium

Modify default executablePath for arm64

path: node_modules/puppeteer-core/lib/cjs/puppeteer/node/Launcher.js
change: '/usr/bin/chromium-browser' -> '/opt/homebrew/bin/chromium'