29

When I'm trying to execute my <configuration>.js file, I'm getting the error below:

[14:49:13] I/launcher - Running 1 instances of WebDriver
[14:49:13] I/direct - Using ChromeDriver directly...
[14:49:13] E/direct - Error code: 135
[14:49:13] E/direct - Error message: Could not find update-config.json. Run 'webdriver-manager update' to download binaries.
[14:49:13] E/direct - Error: Could not find update-config.json. Run 'webdriver-manager update' to download binaries.

I ran the command webdriver-manager update and tried to execute the file, but the same error persists. Can anyone help me to overcome the same?

funnydman
  • 9,083
  • 4
  • 40
  • 55
KAK
  • 905
  • 4
  • 14
  • 33

4 Answers4

60

Using node node_modules/protractor/bin/webdriver-manager update worked for me.

WestCoastProjects
  • 58,982
  • 91
  • 316
  • 560
tbo47
  • 2,688
  • 3
  • 20
  • 11
17

directConnect does not use the global installed version but the version that is provided by Protractor in node_modules/protractor/node_modules/webdriver-manager/. You will need to update that one.

If you have a global version installed the command webdriver-manager update will update the global installed webdriver-manager. If you have a global installed version please remove it, or don't use the directConnect and adjust you protractor config with seleniumAddress: 'http://localhost:4444/wd/hub/'

Hope it helps

wswebcreation
  • 2,365
  • 2
  • 10
  • 18
  • 1
    This worked for me. I set directConnect to false, added seleniumAddress and ran webdriver-manager start – santon Jul 14 '17 at 21:10
  • 2
    fwiw my local webdriver manager was here node_modules/protractor/bin/webdriver-manager update – CodeMonkey Nov 05 '18 at 14:12
1

If you don't want to run: node node_modules/protractor/bin/webdriver-manager update you can also write a script in package.json. For example: "e2e:update-webdriver": "webdriver-manager update --gecko false"

Calling it with npm run e2e:update-wedriver solved the error in my case.

Hope it helps!

Eduard Frankford
  • 151
  • 9
0

I had this error in VSCode after I upgraded to angular-cli v6.0.8. Trying to change the protractor.conf file to use directConnect: false and add a seleniumAddress didn't work for me.

However, I was able to fix this by simply stopping any running server (or lite server instances), restart VSCode, and restart the servers. I'm now able to run protractor 5.3.0 with @angular/cli 6.0.8 while still using directConnect: true.

nanoTitan
  • 562
  • 4
  • 7