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

Chromedriver exited with error code: null error (MacOS) #41

Open
cenkingunlugu opened this issue Apr 5, 2019 · 4 comments
Open

Chromedriver exited with error code: null error (MacOS) #41

cenkingunlugu opened this issue Apr 5, 2019 · 4 comments

Comments

@cenkingunlugu
Copy link

For a project, I am trying to run electron-chromedriver but I am getting these errors:

./node_modules/.bin/chromedriver -h                   

dyld: Library not loaded: @rpath/libffmpeg.dylib
  Referenced from: /Users/cxe10/workspace/FluxToolUiTests/node_modules/electron-chromedriver/bin/chromedriver
  Reason: image not found
/Users/cxe10/workspace/FluxToolUiTests/node_modules/electron-chromedriver/chromedriver.js:18
    throw new Error(`Chromedriver exited with error code: ${code}`)
    ^

Error: Chromedriver exited with error code: null
    at ChildProcess.chromeDriverProcess.on.code (/Users/cxe10/workspace/FluxToolUiTests/node_modules/electron-chromedriver/chromedriver.js:18:11)
    at ChildProcess.emit (events.js:189:13)
    at maybeClose (internal/child_process.js:970:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)

MacOSX Version: 10.14.4 (18E226)
Node Version: v10.15.3
Npm Version: 6.4.1
electron-chromedriver version: ^5.0.0-beta.1

@PedroPauloML
Copy link

Same error

@mandaarp
Copy link

For me as well.

@evertonlperes
Copy link

Got the same error in CI, running on macOS BigSur:

── [email protected]
└─┬ [email protected]
  └─┬ @electron/[email protected]
    └── [email protected] deduped

└─┬ [email protected]
  └── [email protected]

Have you guys found a solution?

Thanks!

@ghost
Copy link

ghost commented Nov 19, 2021

I personally found that most if not all driver related errors I ever had were handled by using selenium-webdriver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants