ChromeDriver could not be found #164

dcsan · 2016-12-25T20:42:10Z

This is just an information since others have the same problem... or if you know the reason.

I setup wechaty on two new machines (showing it to a friend) and both times hit this error on trying to run the demo. However I don't always hit this problem - other machines have been OK.

ChromeDriver could not be found

INFO Wechaty v#git[044d24f 0.6.67] initializing...
ERR PuppetWebBrowserDriver initChromeDriver() Wechaty require `chrome-driver` to be installed.
ERR PuppetWebBrowser init() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
WARN PuppetWebBrowser quit() exception: Cannot read property 'close' of undefined
WARN PuppetWebBrowser driver.quit() exception: Cannot read property 'close' of undefined
ERR PuppetWeb initBrowser() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
ERR PuppetWeb init() exception: Error: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
    at Error (native)
    at ServiceBuilder (/Users/dc/dev/rikai/ta-bot/wechaty/node_modules/selenium-webdriver/chrome.js:191:13)
    at getDefaultService (/Users/dc/dev/rikai/ta-bot/wechaty/node_modules/selenium-webdriver/chrome.js:280:22)
    at Function.createSession (/Users/dc/dev/rikai/ta-bot/wechaty/node_modules/selenium-webdriver/chrome.js:700:44)
    at createDriver (/Users/dc/dev/rikai/ta-bot/wechaty/node_modules/selenium-webdriver/index.js:167:33)
    at Builder.build (/Users/dc/dev/rikai/ta-bot/wechaty/node_modules/selenium-webdriver/index.js:639:16)
    at BrowserDriver.<anonymous> (/Users/dc/dev/rikai/ta-bot/wechaty/src/puppet-web/browser-driver.js:79:26)
    at next (native)
    at /Users/dc/dev/rikai/ta-bot/wechaty/src/puppet-web/browser-driver.js:7:65
    at __awaiter (/Users/dc/dev/rikai/ta-bot/wechaty/src/puppet-web/browser-driver.js:3:12)
INFO Bot error: Error: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
(node:21414) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: can not say before login
(node:21414) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'quit' of undefined

To fix this i reinstalled just

npm i chromedriver

and everything was OK.

Now I noticed the URL points to a google domain.

http://chromedriver.storage.googleapis.com

But since it came from (c)npm i was able to install OK.

The text was updated successfully, but these errors were encountered:

huan · 2016-12-26T03:56:58Z

This is expected because I removed the chromedriver dependence in wechaty at 9e7164f

The reason I do this is because we will have many heads in the future, now we have two: phantomjs and chromedriver, later maybe we need android SDK/Emulator, etc. So I think to let the user install the exact dependence instead of we install everything is a better choice.

Also, there's another problem when you in China: you can use CDN from Taobao for npm, but chromedriver is hosted at another google server, so you have to set another proxy for installing chromedriver. It's will block some user to install Wechaty.

Finally, if you think we should include the chromedriver in Wechaty, we can discuss it as well. Because I'm not very sure if we should include it or not. Thanks.

dcsan · 2016-12-27T01:39:44Z

I think this needs to be documented then, as currently it will (sometimes?) leave an incomplete install. One way would be an installer/setup script, but that would need to also maybe support windows which would be a pain.

Is there a way to use PhantomJS in development, or is that just for testing? I tried:

const TestConfig = {
  "wechaty": {
    "profile": "TABOT",
    "DEFAULT_HEAD": "phantomjs", // chrome
    "DEFAULT_PUPPET": "web",
    "DEFAULT_PROFILE": "demo",
    "DEFAULT_PORT": 8788,
    "DEFAULT_PROTOCOL": "io|0.0.1",
    "DEFAULT_TOKEN": "WECHATY_IO_TOKEN",
    "DEFAULT_APIHOST": "api.wechaty.io",
    "CMD_CHROMIUM": "/wechaty/bin/xvfb-chromium"
  }
}

const WcBot = Wechaty.instance( TestConfig.wechaty );

huan · 2016-12-28T23:01:15Z

Yes, I agree that this should be documented, because it will always leave an incomplete install.

Wechaty should be able to use PhantomJS in development, but as I'm not using it for months, there might have some issue, see also #60 #163

eastmoon · 2017-01-05T08:57:52Z

I have same problem.

Today, i need find some solution with WeChat bot.
And, i try wechaty by below step.

1 npm install --save wechaty
2 npm install chromedriver
3 create mybot.js and copy code : 6 lines of JavaScrip
4 node mybot.js

Then, i have same problem with wechaty could not find chromedriver.
For node.js, i am newbie, i use all i know to find answers, but still not idea how to solve.

huan · 2017-01-05T12:31:24Z

Hi @eastmoon ,

TL;DR

I suggest you install chromedriver globally by run npm install -g chromedriver, then you can find chromedriver in your PATH.

Detail

Your issue is because chromedriver is not in your current PATH, so you can not run it.

After you ran npm install chromedriver, the chromedriver will be placed at ./node_modules/.bin/, but this directory is not in your PATH by default.

As a result, Wechaty will also not be able to find it.

dcsan · 2017-01-08T18:23:49Z

This issue came up in another chatroom today too. It seems a frequent issue.
if we can't fix the install process then perhaps some code could try to detect if chromedriver can be found or not, and then put an error message with fix advice.

huan · 2017-01-09T08:42:29Z

@dcsan Yes, I agree with you.

I'm planning to put the chromedriver detection in npm run doctor: if there's no chromedriver found in the system, the npm run doctor will print a user-friendly error message and the suggestion of how to fix that.

huan · 2017-01-09T08:52:01Z

@dcsan @eastmoon at last, I decided to restore chromedriver dependence, because it seems the simplest solution for this kind of issue. :P

eastmoon · 2017-01-10T06:55:58Z

@zixia Good decided.
I will try again in a few day late.
Hope this issue will be fix.

brianwfl88 · 2017-02-07T13:26:02Z

Hi, I am having the same issue like eastmoon

I can run chromedriver command just fine, and also added chromedriver PATH from global scope.

My box is Window 7 64-bit, updated with latest node 7.5, npm 4.1.2

ax4 · 2017-02-09T04:56:07Z

Same as @brianwfl88

I can run chromedriver in cmd, it's already in PATH. But it still fail at ChromeDriver.

My box is Windows 10 64-bit, with node ~~~v6.9.1~~~ v6.9.5, npm ~~~v3.10.8~~~ v3.10.10

huan · 2017-02-09T05:28:25Z

Hi @brianwfl88 @ax4 ,

It seems you guys are both using windows.

Could you please provide the follow information for diagnosing?

the source code of your program
the command line command of starting your program
the full output of logs with WECHATY_LOG=verbose

ax4 · 2017-02-09T05:36:14Z

I just copy from README in my app.js

const { Wechaty } = require('wechaty')

Wechaty.instance() // Singleton
    .on('scan', (url, code) => console.log(`Scan QR Code to login: ${code}\n${url}`))
    .on('login', user => console.log(`User ${user} logined`))
    .on('message', message => console.log(`Message: ${message}`))
    .init()

And I start it as node app.js from cmd

The whole error message pop-out in cmd is

INFO Wechaty v0.7.17 initializing...
ERR PuppetWebBrowserDriver initChromeDriver() Wechaty require `chrome-driver` to be installed.
ERR PuppetWebBrowser init() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
WARN PuppetWebBrowser quit() exception: Cannot read property 'close' of undefined
WARN PuppetWebBrowser driver.quit() exception: Cannot read property 'close' of undefined
ERR PuppetWeb initBrowser() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
ERR PuppetWeb init() exception: Error: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
    at Error (native)
    at ServiceBuilder (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\chrome.js:191:13)
    at getDefaultService (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\chrome.js:280:22)
    at Function.createSession (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\chrome.js:700:44)
    at createDriver (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\index.js:167:33)
    at Builder.build (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\index.js:639:16)
    at BrowserDriver.<anonymous> (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\wechaty\dist\src\puppet-web\browser-driver.js:111:26)
    at next (native)
    at C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\wechaty\dist\src\puppet-web\browser-driver.js:7:71
    at __awaiter (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\wechaty\dist\src\puppet-web\browser-driver.js:3:12)
ERR Wechaty init() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
ERR Config ###########################
ERR Config unhandledRejection: Error: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH. [object Promise]
ERR Config ###########################
ERR Config unhandledRejection::catch(The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.)
(node:12472) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2)

And with pop-out with set WECHATY_LOG=verbose

VERB Wechaty contructor()
VERB Wechaty addListener(scan, function)
VERB Wechaty addListener(login, function)
VERB Wechaty addListener(message, function)
INFO Wechaty v0.7.17 initializing...
VERB Wechaty puppet: web
VERB Wechaty head: chrome
VERB Wechaty profile: null
VERB Wechaty uuid: 70127a55-b9d7-4128-ad76-6b1ac1e8ee2b
VERB StateMonitor Wechaty:target(ready) <- (standby)
VERB StateMonitor Wechaty:current(ready,false) <- (standby,true)
VERB Config puppetInstance(PuppetWeb)
VERB PuppetWeb init() with head:chrome, profile:null
VERB StateMonitor Puppet:target(live) <- (dead)
VERB StateMonitor Puppet:current(live,false) <- (dead,true)
VERB PuppetWeb init() getPort 19459
VERB PuppetWeb initServer()
VERB PuppetWebServer init() on port 19459
VERB PuppetWebServer createHttpsServer() listen on port 19459
VERB PuppetWeb initServer() done
VERB PuppetWeb initBrowser()
VERB PuppetWebBrowser constructor() with head(chrome) sessionFile(null)
VERB PuppetWebBrowserDriver constructor(chrome)
VERB PuppetWebBrowserCookie constructor(BrowserDriver, )
VERB PuppetWebBrowser init()
VERB StateMonitor Browser:target(open) <- (close)
VERB StateMonitor Browser:current(open,false) <- (close,true)
VERB PuppetWebBrowserCookie hostname()
VERB PuppetWebBrowserCookie getCookiesFromFile() from "undefined"
VERB PuppetWebBrowserDriver init() for head: chrome
VERB PuppetWebBrowserDriver initChromeDriver()
VERB PuppetWebBrowserDriver initChromeDriver() new Builder()
ERR PuppetWebBrowserDriver initChromeDriver() Wechaty require `chrome-driver` to be installed.
ERR PuppetWebBrowser init() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
VERB PuppetWebBrowser quit()
VERB StateMonitor Browser:target(close) <- (open)
VERB StateMonitor Browser:current(close,false) <- (open,false)
WARN PuppetWebBrowser quit() exception: Cannot read property 'close' of undefined
WARN PuppetWebBrowser driver.quit() exception: Cannot read property 'close' of undefined
VERB StateMonitor Browser:current(close,true) <- (close,false)
ERR PuppetWeb initBrowser() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
ERR PuppetWeb init() exception: Error: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
    at Error (native)
    at ServiceBuilder (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\chrome.js:191:13)
    at getDefaultService (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\chrome.js:280:22)
    at Function.createSession (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\chrome.js:700:44)
    at createDriver (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\index.js:167:33)
    at Builder.build (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\selenium-webdriver\index.js:639:16)
    at BrowserDriver.<anonymous> (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\wechaty\dist\src\puppet-web\browser-driver.js:111:26)
    at next (native)
    at C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\wechaty\dist\src\puppet-web\browser-driver.js:7:71
    at __awaiter (C:\Users\x7180\Documents\Visual Studio 2017\Projects\WeChatyTest\WeChatyTest\node_modules\wechaty\dist\src\puppet-web\browser-driver.js:3:12)
ERR Wechaty init() exception: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
ERR Config ###########################
ERR Config unhandledRejection: Error: The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH. [object Promise]
ERR Config ###########################
ERR Config unhandledRejection::catch(The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.)
(node:1880) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2)

huan · 2017-02-09T07:22:24Z

@ax4

Had you tried to install an NPM version of chromedriver?

like run this:

npm install chromedriver

brianwfl88 · 2017-02-09T09:06:15Z

Hi @zixia,

I have noticed my console is trying to load chrome-driver.

However you suggest to install chromedriver. Will that be an issue? Since "chrome-driver" and "chromedriver" are different things and "chrome-driver" could not be found in npm repository.

huan · 2017-02-09T09:11:57Z

It should be chromedriver. ~~chrome-driver~~ is my typo, sorry for that.
9a5b6f0

Did npm install chromedriver fix this issue for you?

ax4 · 2017-02-09T09:31:56Z

Hi @zixia,

my chromedriver was installed by npm install -g chromedriver , and it was added to PATH by that.

Although I tried npm install chromedriver this time, but it still won't work.

Plus: my wechaty is also installed from npm, and it's on version 0.7.17 (described by the package itself)

huan · 2017-02-09T09:45:32Z

@ax4 Sorry for that not work for you. It seems you had run into an unknown state for me.

There's a win32 CI setting file of appveyor at here:
https://github.com/wechaty/wechaty/blob/master/appveyor.yml

It runs under Windows without any problem; you might be able to make chromedriver work for you by inspecting this file.

Good luck!

brianwfl88 · 2017-02-09T12:13:01Z

I have added "E:\wamp\www\GitHub\wechaty\node_modules\chromedriver\bin" into both System Path and User Path.

Some related issue with chrome driver on binary path: https://github.com/angular/protractor/issues/950

INFO Wechaty v0.7.17 initializing... WARN PuppetWebBrowserDriver valid() getSession() catch() rejected: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver valid() driver.getSession() exception: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver initChromeDriver() got invalid driver WARN PuppetWebBrowserDriver initChromeDriver() with retry: 1 ERR Config ########################### ERR Config unhandledRejection: WebDriverError: unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) [object Promise] ERR Config ########################### ERR Config unhandledRejection::catch(unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64)) (node:6460) PromiseRejectionHandledWarning: Promise rejection was handled asynch ronously (rejection id: 1) WARN PuppetWebBrowserDriver valid() getSession() catch() rejected: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver valid() driver.getSession() exception: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver initChromeDriver() got invalid driver WARN PuppetWebBrowserDriver initChromeDriver() with retry: 2 ERR Config ########################### ERR Config unhandledRejection: WebDriverError: unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) [object Promise] ERR Config ########################### ERR Config unhandledRejection::catch(unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64)) (node:6460) PromiseRejectionHandledWarning: Promise rejection was handled asynch ronously (rejection id: 2) WARN PuppetWebBrowserDriver valid() getSession() catch() rejected: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver valid() driver.getSession() exception: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver initChromeDriver() got invalid driver WARN PuppetWebBrowserDriver initChromeDriver() with retry: 3 ERR Config ########################### ERR Config unhandledRejection: WebDriverError: unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) [object Promise] ERR Config ########################### ERR Config unhandledRejection::catch(unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64)) (node:6460) PromiseRejectionHandledWarning: Promise rejection was handled asynch ronously (rejection id: 3) WARN PuppetWebBrowserDriver valid() getSession() catch() rejected: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver valid() driver.getSession() exception: unknown error : cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) WARN PuppetWebBrowserDriver initChromeDriver() got invalid driver WARN PuppetWebBrowserDriver initChromeDriver() not valid after retry: 4 times: E rror: initChromeDriver() got invalid driver at BrowserDriver.<anonymous> (E:\wamp\www\GitHub\wechaty\node_modules\wechat y\dist\src\puppet-web\browser-driver.js:116:35) at Generator.next (<anonymous>) at fulfilled (E:\wamp\www\GitHub\wechaty\node_modules\wechaty\dist\src\puppe t-web\browser-driver.js:4:58) at process._tickCallback (internal/process/next_tick.js:103:7) ERR PuppetWebBrowser init() exception: initChromeDriver() got invalid driver ERR PuppetWebBrowser quit() this.driver.quit() exception unknown error: cannot f ind Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) ERR Config ########################### ERR Config unhandledRejection: WebDriverError: unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64) [object Promise] ERR Config ########################### ERR Config unhandledRejection::catch(unknown error: cannot find Chrome binary (Driver info: chromedriver=2.27.440174 (e97a722caafc2d3a8b807ee115bfb307f7d2cf d9),platform=Windows NT 6.1.7601 SP1 x86_64)) (node:6460) PromiseRejectionHandledWarning: Promise rejection was handled asynch ronously (rejection id: 4) ERR PuppetWeb initBrowser() exception: initChromeDriver() got invalid driver ERR PuppetWeb init() exception: Error: initChromeDriver() got invalid driver at BrowserDriver.<anonymous> (E:\wamp\www\GitHub\wechaty\node_modules\wechat y\dist\src\puppet-web\browser-driver.js:116:35) at Generator.next (<anonymous>) at fulfilled (E:\wamp\www\GitHub\wechaty\node_modules\wechaty\dist\src\puppe t-web\browser-driver.js:4:58) at process._tickCallback (internal/process/next_tick.js:103:7) ERR Wechaty init() exception: initChromeDriver() got invalid driver ERR Config ########################### ERR Config unhandledRejection: Error: initChromeDriver() got invalid driver [obj ect Promise] ERR Config ########################### ERR Config unhandledRejection::catch(initChromeDriver() got invalid driver) (node:6460) PromiseRejectionHandledWarning: Promise rejection was handled asynch ronously (rejection id: 6) WARN PuppetWebBrowserDriver valid() driver.getSession() timeout(halt?) WARN PuppetWebBrowserDriver valid() driver.getSession() timeout(halt?) WARN PuppetWebBrowserDriver valid() driver.getSession() timeout(halt?) WARN PuppetWebBrowserDriver valid() driver.getSession() timeout(halt?)

huan · 2017-02-09T12:40:45Z

@brianwfl88 According to the error message: unknown error : cannot find Chrome binary

This time it seems that you need to install chrome browser.

ax4 · 2017-02-09T12:57:59Z

@zixia Anyway, thank you so much for your help! I really appreciate it!

Your docker solution is awesome! I'll keep going on bot development with docker solution, as well as figure out how it works on win32 (hopefully someday😅).

BTW, I was so much impressed by your Wechaty 101 Video. Honestly, I have so much essentials to learn - from Docker thru CI, and Testing thru Building. Thanks to Wechaty project! It inspires me a lot!

huan · 2017-02-09T14:38:21Z

@ax4 Thanks for loving Wechaty, appreciate it. :)

brianwfl88 · 2017-02-12T15:57:36Z

hi @zixia ,

The program is running fine now on another windows machine, the chromedriver path must use .exe in the 'lib' folder.

After that, the demo script works fine. Thank you for your help.

huan · 2017-02-12T16:38:05Z

@brianwfl88 Great to hear that, Cheers!

huan added the question label Dec 26, 2016

huan closed this as completed in 1acdbf6 Jan 9, 2017

huan reopened this Feb 9, 2017

huan added a commit that referenced this issue Feb 10, 2017

better error message for chromedriver #164

288f828

huan closed this as completed Feb 12, 2017

huan mentioned this issue Jul 21, 2017

Just remove the chromedriver dependency #674

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ChromeDriver could not be found #164

ChromeDriver could not be found #164

dcsan commented Dec 25, 2016

huan commented Dec 26, 2016 •

edited

Loading

dcsan commented Dec 27, 2016

huan commented Dec 28, 2016

eastmoon commented Jan 5, 2017

huan commented Jan 5, 2017

dcsan commented Jan 8, 2017 •

edited

Loading

huan commented Jan 9, 2017 •

edited

Loading

huan commented Jan 9, 2017

eastmoon commented Jan 10, 2017

brianwfl88 commented Feb 7, 2017 •

edited

Loading

ax4 commented Feb 9, 2017 •

edited

Loading

huan commented Feb 9, 2017

ax4 commented Feb 9, 2017 •

edited

Loading

huan commented Feb 9, 2017 •

edited

Loading

brianwfl88 commented Feb 9, 2017 •

edited

Loading

huan commented Feb 9, 2017 •

edited

Loading

ax4 commented Feb 9, 2017 •

edited

Loading

huan commented Feb 9, 2017

brianwfl88 commented Feb 9, 2017

huan commented Feb 9, 2017

ax4 commented Feb 9, 2017

huan commented Feb 9, 2017

brianwfl88 commented Feb 12, 2017

huan commented Feb 12, 2017

ChromeDriver could not be found #164

ChromeDriver could not be found #164

Comments

dcsan commented Dec 25, 2016

huan commented Dec 26, 2016 • edited Loading

dcsan commented Dec 27, 2016

huan commented Dec 28, 2016

eastmoon commented Jan 5, 2017

huan commented Jan 5, 2017

TL;DR

Detail

dcsan commented Jan 8, 2017 • edited Loading

huan commented Jan 9, 2017 • edited Loading

huan commented Jan 9, 2017

eastmoon commented Jan 10, 2017

brianwfl88 commented Feb 7, 2017 • edited Loading

ax4 commented Feb 9, 2017 • edited Loading

huan commented Feb 9, 2017

ax4 commented Feb 9, 2017 • edited Loading

huan commented Feb 9, 2017 • edited Loading

brianwfl88 commented Feb 9, 2017 • edited Loading

huan commented Feb 9, 2017 • edited Loading

ax4 commented Feb 9, 2017 • edited Loading

huan commented Feb 9, 2017

brianwfl88 commented Feb 9, 2017

huan commented Feb 9, 2017

ax4 commented Feb 9, 2017

huan commented Feb 9, 2017

brianwfl88 commented Feb 12, 2017

huan commented Feb 12, 2017

huan commented Dec 26, 2016 •

edited

Loading

dcsan commented Jan 8, 2017 •

edited

Loading

huan commented Jan 9, 2017 •

edited

Loading

brianwfl88 commented Feb 7, 2017 •

edited

Loading

ax4 commented Feb 9, 2017 •

edited

Loading

ax4 commented Feb 9, 2017 •

edited

Loading

huan commented Feb 9, 2017 •

edited

Loading

brianwfl88 commented Feb 9, 2017 •

edited

Loading

huan commented Feb 9, 2017 •

edited

Loading

ax4 commented Feb 9, 2017 •

edited

Loading