Ytukyg

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:UsersNEWAppDataLocal...}, 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}

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. Hope this helps!

TL;DR: run npm install -g chromedriver

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.

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

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

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

npm install chromedriver --chromedriver_version=LATEST

Changing latest version of ChromDriver worked for me.

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