org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'
Asked Answered
M

8

66

Sendkeys not working. Please help me to resolve this..

WebElement username = driver.findElement(By.xpath("//*[@id='username']"));      
username.sendKeys("123456");

Console:

Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

  (Session info: chrome=65.0.3325.31)
  (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86) 
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
System info: host: 'NEW-PC', ip: '192.168.0.103', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_161'

Driver info:

org.openqa.selenium.chrome.ChromeDriver

Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506120 (e3e53437346286..., userDataDir: C:\Users\NEW\AppData\Local\...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.31, webStorageEnabled: true}
Mensal answered 4/2, 2018 at 14:23 Comment(0)
B
114

I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.

It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved.

TL;DR: run npm install -g chromedriver

Brabant answered 7/2, 2018 at 13:36 Comment(11)
Thanks! It worked. Updated the chrome driver to 2.35Mensal
You're welcome. If the answer solves your problem, it's customary to mark it as "accepted answer".Brabant
chromedriver v2.35 supports chrome 62-64 at the momentGiralda
I updated this to 2.38.0, But when I check the version, it always says 2.33. I have changed the package.config (Visual Studio C#)...I cannot find any reference to 2.33 anymore. Where could this be? I tried to delete the project and recreate it.I am using the standalone selenium server..Buehler
my chromedriver didn't automatically update in katalon studio. why is this and what can I do about it?Schoonmaker
Performed chromedriver update in visual studio with NuGet package Manager and everything works fine as before.Encephalography
This solution doesn't work. i have chrome 71 and driver version 2.45Closelipped
@Closelipped did you find any solution to this problem? It's been almost 2 days, I can't find the solutionExpurgatory
@YashwardhanPauranik, Yes i found. refer this #53884018Closelipped
@Closelipped Thanks bro..I'll look into thisExpurgatory
I just need to put a new args to force to update the chromedriver because of already existed an version installed. npm install -g --force chromedriverLiberalism
C
16

The error says it all :

Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'

  (Session info: chrome=65.0.3325.31)
  (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 6.1.7601 SP1 x86) 
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'  

Your main issue is the version compatibility between the binaries you are using as follows :

  • You are using chromedriver=2.33
  • Release Notes of chromedriver=2.33 clearly mentions the following :

Supports Chrome v60-62

  • You are using chrome=65.0
  • Release Notes of ChromeDriver v2.37 clearly mentions the following :

Supports Chrome v64-66

So there is a clear mismatch between the ChromeDriver version (v2.33) and the Chrome Browser version (v65.0)

Solution

  • Upgrade ChromeDriver to current ChromeDriver v2.37 level.
  • Keep Chrome version at Chrome v65.x levels. (as per ChromeDriver v2.37 release notes)
  • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
  • Use CCleaner tool to wipe off all the OS chores before and after the execution of your test Suite.
  • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.
  • Execute your @Test.
Cobble answered 27/3, 2018 at 9:56 Comment(0)
S
3

The latest chrome browser requires corresponding latest chromedriver executable for the tests to run.

Stank answered 13/3, 2018 at 11:36 Comment(0)
C
2

I have encountered the same issue and installed the chrome drive. Issue got resolved.

npm install chromedriver --chromedriver_version=LATEST

Chris answered 13/3, 2018 at 9:1 Comment(0)
M
2

Changing latest version of ChromDriver worked for me.

Monochromatism answered 19/3, 2018 at 4:53 Comment(0)
M
1

You may need to update you driver the link for all the chromedriver updates are http://chromedriver.storage.googleapis.com/index.html make sure you chromedriver corresponds to your version of chrome

Maximomaximum answered 16/3, 2018 at 18:58 Comment(0)
F
0

I simply installed a new version of Katalon Studio and it has worked fine.

Fenugreek answered 28/3, 2018 at 13:58 Comment(1)
Sorry but this solution (if correct) highly depends on the workflow of the user who posted the question. Introducing a new tool when there's no real need looks like a desperate attempt to solve the issue without really understanding the nature/source of the problem.Fall
T
0

This issue happens when chrome and chromedriver are not in sync. Either update both to the latest version or make sure they can work together. After running the following commands it worked for me

npm install -g chromedriver --chromedriver-force-download
webdriver-manager update
Therefor answered 6/11, 2019 at 1:51 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.