Dusk: Chrome 65 (now released in beta channel) requires new chromedriver

[pdbreen]

After Chrome65 was installed, my dusk tests that attempt to input values are failing with the following error:

Facebook\WebDriver\Exception\UnknownServerException: unknown error: call function result missing 'value'
  (Session info: chrome=65.0.3325.51)
  (Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 10.0.16299 x86_64)

D:\src\jrweb\vendor\facebook\webdriver\lib\Exception\WebDriverException.php:114
D:\src\jrweb\vendor\facebook\webdriver\lib\Remote\HttpCommandExecutor.php:320
D:\src\jrweb\vendor\facebook\webdriver\lib\Remote\RemoteWebDriver.php:535
D:\src\jrweb\vendor\facebook\webdriver\lib\Remote\RemoteWebDriver.php:296
D:\src\jrweb\vendor\laravel\dusk\src\Browser.php:336
D:\src\jrweb\vendor\laravel\dusk\src\Concerns\InteractsWithElements.php:72

A post on Stack Overflow suggests upgrading chromedriver to version 2.35 will resolve. I've confirmed this is true by locally swapping in the latest driver and verifying the tests run properly again.

[kamui545]

PR open https://github.com/laravel/dusk/pull/468

[pdbreen]

Fixed by PR #469 and released in 3.0.2. Thanks @themsaid

[ian-nisbet]

Please @themsaid can you update the binaries in Dusk v1, and v2. Those of us still using Laravel 5.4 and 5.5 have to use the older Dusk versions.

As a manual workaround, I installed a new Laravel 5.6, installed Dusk ~3.0, then manually copied the driver files from vendor/dusk/bin to my project vendor/dusk/bin.

All would be fine, except that I also had to kill the previously running chromedriver process in Mac Activity Monitor (https://www.reddit.com/r/laravel/comments/82q4an/getting_strange_failures_in_dusk_and_wrong/)

[staudenmeir]

I created an Artisan command for updating the ChromeDriver binaries on all Dusk versions: https://github.com/staudenmeir/dusk-updater