webdriver-manager: Error for missing update-config.json does not resolve the issue

@danielwashbrook 's comment was helpful to me. Essentially, it seems that the error happens because you update webdriver at the system level, but not the one used internally by protractor. Try which webdriver-manager to see which one you run by default. To update specifically the one used by Protractor, you have to specify the path explicitly, like for example (starting from the root directory of your repo): ./node_modules/protractor/bin/webdriver-manager update --versions.chrome 2.35 The version argument is optional, running without it will update to the latest version.

I ran into the same error you’re referring to. What I found was webdriver-manager was installed in a few different places. If you installed it explicitly with npm, it’s in your path. But protractor also installs it in it’s own node_modules and that’s the one that’s looking for the config. So you need to run the update on the version in the protractor module and then start that same version for protractor to connect to.

@danielwashbrook that was it for me. Once I ran $ ./node_modules/protractor/node_modules/webdriver-manager/bin/webdriver-manager update

Then protractor worked. Thanks!

Please make sure to install npm install protractor

Update web driver manager webdriver-manager update

Run this command from your root node node_modules\protractor\bin\webdriver-manager update

Now start up a server with: webdriver-manager start

Also make sure that your protractor.conf.js file has below line // baseUrl: 'http://localhost:4200/', seleniumAddress: 'http://localhost:4444/wd/hub/',

Now run your e2e tests on different browsers ng e2e

This is not an issue with webdriver-manager…it looks like you are confusing the local node modules directory with global. Protractor is looking for the local file update-config.json in the local project node modules directory. The binaries should be installed in:project-dir/node_modules/protractor/node_modules/webdriver-manager/selenium/. I just answered this question on StackOverflow. See:

https://stackoverflow.com/questions/42426549/protractor-in-sts-ide-could-not-find-update-config-json/42453067#42453067

Run >>> npx webdriver-manager update It should fix the issue!!

Great guys!!! I can confirm this on travis as well https://travis-ci.com/jsGanttImproved/jsgantt-improved/builds/95386323

i added this on travis.yml

install:
  - npm install
  - ./node_modules/protractor/bin/webdriver-manager update --versions.chrome 2.35

Thanks

When running Protractor with directConnect, we refer to the latest on the update-config.json. So how can we side step the whole problem for Protractor? Before we talk about the two examples, the magic is to override the chromeDriver path. You can see that we check the chromeDriver path from the config before considering to use the update-config.json (angular/protractor driverProvider/direct.ts#63)

Running into a GitHub API limit

Some final thoughts on this. Webdriver-manager can hit a GitHub API limit which can be problematic on CI. Possibly the solution is to follow the next step about how to use a global install. If you do not have to run FireFox, then you could add the flag --gecko false when calling update.

Using a global install of webdriver-manager could help

In an environment like Jenkins, you could run a global webdriver-manager update. After you run it once, you could read the global webdriver-manager update-config.json. From the content, you could parse out the latest chromedriver path, and pass it to the protractor command line with protractor yourconfig.js --chromeDriver=/looked/up/path/to/chromedriver.

Completely side step webdriver-manager and wget

In an environment you do not control, you might want a specific chromedriver version, you could just do a wget on the chromedriver. The list of chromedriver versions is here: https://chromedriver.storage.googleapis.com/index.html. From there you could still pass the path to the chromedriver to Protractor via command line.

@nishankkumar1994 node ./node_modules/protractor/bin/webdriver-manager update

In my case the error happens because of custom copy of protractor module inside grunt-protractor-runner (./node_modules/grunt-protractor-runner/node_modules/protractor/bin/webdriver-manager).

Run >>> sudo node_modules/protractor/bin/webdriver-manager update and then it should work

Thanks @SebastianKristof! I fixed it by following his instruction.

Following blog is useful, last two steps are helpful that is swapping node.exe from your installed directory to eclipse plugin directory:

https://khyatisehgal.wordpress.com/2014/09/17/812/

A couple of weeks back I faced the same issue in MAC. This is what I did, find all chrome|gecko|xyz driver and kill all the process. Uninstall protractor from global and from local workspace. Do a fresh install of the protractor hopefully, should solve the problem.