Can't specify ChromeDriver 76 or any other versions on webdriver-manager update #404
Comments
jumjamjohn
changed the title
jumjamjohn
changed the title
|
have created a pull request for this #405 |
|
I am facing the same issue |
|
Thank you, @MathRobin. I didn't know it was just config.json. Hope it'll get merged soon. For those who have the same problem, I solved this by removing |
|
Published 12.1.6. Thank you @MathRobin for creating the PR and thank you for creating the issue and discussion. |
|
Hello Nicolas ,
Please try this : Go to node modules >protractor folder and run npm i
webdriver-manager@latest
When you update the webdriver , it again picks up the chrome driver present
in the above folder .Hope it helps :)
…On Wed, Aug 7, 2019 at 5:33 AM Nicolas Breitwieser ***@***.***> wrote:
I don't get it. As I understand it, all the PRs referenced in this issue
are just workarounds to make it work with Travis to switch back to Chrome
<76 (please forgive me if I'm wrong).... but how does it actually work with
Chrome 76? I'm not a travis user and neet protractor to run on my very own
machine ... I tried webdriver-manager update --chrome (even with exact
Chrome version given), but it didn't work ... any hints, anybody?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#404?email_source=notifications&email_token=AKPMTHVLBBIXQCACRO4RMKDQDJGDFA5CNFSM4IIEUN42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3XFJDY#issuecomment-518935695>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKPMTHWWNZPZDXFFKL63HTTQDJGDFANCNFSM4IIEUN4Q>
.
--
Regards,
Dolly Agarwal
+44-7305736794
|
|
Hi @Dolly2315 Thank you very much for your instantaneous response and explanation. I've figured out to update webdriver-manager, too, that's why I've deleted my post a few minutes later. The only thing is that I now have errors telling me something about "circular reference" (which forced me into using a different machine for now where the "old" setup using Chrome 75 is still running). However this error is unrelated to this thread. Regards |
|
@Dolly2315's solution worked for me just now, after a few hours of trying to get webdriver-manager to update, then trying to work out why the latest version with support for chromedriver 76 wasn't working...thanks @Dolly2315! |
|
Confirming @Dolly2315's solution worked for me as well. Not going to be a long term solution but it's a valid workaround for now. |
|
Unfortunately I didn't have a dependency in |
|
but its still picking up .46
any ideas how do I fix it? [UPDATE] |
Protractor uses its own version of webdriver manager, which is too old to support Chrome 76. * angular/webdriver-manager#404 * angular/protractor#5289 Its really not worth the effort implementing any of the suggested workarounds. For now, the e2e tests on Chrome will simply not be executed on Travis. Once Protractor 5 is updated with the latest webdriver manager version, we can turn them back on again.
…165) Protractor uses its own version of webdriver manager, which is too old to support Chrome 76. * angular/webdriver-manager#404 * angular/protractor#5289 Its really not worth the effort implementing any of the suggested workarounds. For now, the e2e tests on Chrome will simply not be executed on Travis. Once Protractor 5 is updated with the latest webdriver manager version, we can turn them back on again.
|
None of the solutions here works. |
|
@shreyansh1991 Try this it works make a fresh node_modules before using this hot-fix then run |
angular/webdriver-manager#404 (comment) Signed-off-by: Blake Johnson <bstier@chef.io>
angular/webdriver-manager#404 (comment) Signed-off-by: Blake Johnson <bstier@chef.io>
angular/webdriver-manager#404 (comment) Signed-off-by: Blake Johnson <bstier@chef.io>
angular/webdriver-manager#404 (comment) Signed-off-by: Blake Johnson <bstier@chef.io>
angular/webdriver-manager#404 (comment) Signed-off-by: Blake Johnson <bstier@chef.io>
|
In my case, I just installed the missing package and reinstall all deps. npm i -D webdriver-manager
rm -rf node_modules
npm installNext run end-to-end tests one more time: npm run e2e |
I keep seeing the following errors after Chrome 76 got released.
webdriver-manager updatedownloads chromedriver 2.46 and causesError: SessionNotCreatedError: session not created: Chrome version must be between 71 and 75on running protractor.UnhandledPromiseRejectionWarning: Invalid filename. This seems a similar issue to webdriver-manager update downloads an incompatible version of chromedriver #376logs for the first one:
for the second one:
related: #376
The text was updated successfully, but these errors were encountered: