webdriverio: "unknown error: call function result missing 'value'"

after update chromedriver to 2.36 can fix mine https://sites.google.com/a/chromium.org/chromedriver/downloads

For all those who still get the error: are you sure you have updated the actually used dependency to chromedriver? 🙂

If you manage chromedriver yourself, i.e. you execute chromedriver in some Terminal tab before launching your tests, then you should indeed update the executable itself. If, on the other hand, you are executing chromedriver through wdio-selenium-standalone-service, you’ll need to update it to v0.0.10 to get the update.

If you’re using Homebrew and are having trouble updating chromedriver to the latest version (if you installed it with brew install chromedriver) you might need to uninstall it and reinstall it again as it has been migrated to a cask.

Error: No available formula with the name "chromedriver"
It was migrated from homebrew/core to caskroom/cask.
You can access it again by running:
  brew tap caskroom/cask
And then you can install it by running:
  brew cask install chromedriver

TL;DR

brew uninstall chromedriver
brew tap caskroom/cask
brew cask install chromedriver

same issue with chrome 65 unknown error: call function result missing 'value' running chrome Error: An unknown server-side error occurred while processing the command. at elementIdValue("0.22831194167614743-1", "xxx@mailinator.com") - setValue.js:46:80

Having the same issue. I just updated ChromeDriver (now at 2.36.540469) and Chrome (now at 65.0.3325.146), but I am still getting this issue. Have I missed something?

I had the similar issue and despite that I have upgraded to chromedriver 2.36 selenium standalone was still picking up old version 2.33.5 of the chromedriver.

Solution worked for me is :

1. I had to delete repo and clone it
2. npm install
3. npm i selenium-standalone -g // install selenium standalone globally
4. selenium-standalone install // very important step otherwise selenium will still try to point to the old version of the chromedriver.

I hope this helps

Yes, please update the Chromedriver then. Doesn’t seem to be an issue with WebdriverIO.

The OP didn’t mention the way he is running Selenium. If you are using selenium-standalone npm package then in your package.json upgrade to the latest minor versions:

New - working

    "selenium-standalone": "^6.13.0", <---- this bumps the chromedriver version
    "webdriverio": "^4.12.0",

Old - not working

    "selenium-standalone": "^6.12.0",
    "webdriverio": "^4.10.2",

Do again:

1. npm install
2. ./node_modules/.bin/selenium_standalone install then start

See changes: https://github.com/vvo/selenium-standalone/commit/0e5e206342114631742ec6c8bfdd1ffd8bd0e36e#diff-1370e254e90fb1adbfb1bb0264020501R6

Kudos to @christian-bromann and the wdio community for the speed of fixes. The other communities/projects are yet to figure out the issue let alone release a fix.

I’m happy to be a webdriverio user, much love to you all.

Upgraded the ChromeBrowser from 56 to 65 & ChromeDriver to 2.38 and it worked fine for me.

After downloading the latest v2.38 chromedriver, update selenium-standalone and webdriverio, it still doesn’t work. I installed npm chromedriver and it solved everything 😃 npm install chromedriver then require('chromedriver'); in your file

Thanks, this also fixed the issue for us:

“selenium-standalone”: “^6.13.0” “webdriverio”: “^4.12.0”

Updating my package.json to newest versions:

"wdio-selenium-standalone-service": "~0.0.10",
"webdriverio": "~4.12.0"

Solved the issue for me. Thanks!!

I just started having this problem on Windows after updating from Chrome Version 63.0.3239.132 (Official Build) (64-bit) to 65.0.3325.146 (Official Build) (64-bit).

But after updating chromedriver from 2.33 to 2.36, I am no longer seeing this error.