protractor chromedriver version (CLI vs VSC) error

0
votes

I had error because of using old chromedriver. So I used:

  • webdriver-manager clean
  • webdriver-manager update
  • webdriver-manager status

    To update and verirfy chromedriver version 89.0.4389.90

If I run protractor from command line, all tests passed. So OK. But If I run protractor from visual studio mode pressing F5 (debug). I am faced to this error:

E/launcher - Error: SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 87 
Current browser version is 89.0.4389.90 with binary path C:\Program Files\Google\Chrome\Application\chrome.exe
    
Driver info: chromedriver=87.0.4280.20 (c99e81631faa0b2a448e658c0dbd8311fb04ddbd-refs/branch-heads/4280@{#355}),platform=Windows NT 10.0.19042 x86_64

I donť know why because chromedriver should be already updated to version 89.0.4389.90 via webdriver-manager.

1
protractorselenium-chromedriver

1 Answers

1
votes

webdriver manager is an npm package. Any npm package can have 2 different installations - global and local.

Imagine you have multiple projects. For first one you want to use protractor 5.4 for another one protractor 7. So you would just installed them the way every project had its own local protractor.

Then you start working on third project, but you don't install protractor locally. Then it will go to your global packages to see if protractor is there

Apparently your VSC is configured to use local package. And when you run protractor conf.js that will refer to global one.

Use these steps to update your local webdriver manager How can I revert Protractor back to a selected version?