-
-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to solve critical chromedriver 111 issue? #3083
Comments
I got it working by adding it to serenity.conf like this:
|
Thanks @abergmeister. The |
Problem solved! Thanks to both of you. |
Unfortunately, I cannot use firefox driver "-Dwebdriver.driver=firefox" when defining chrome options the above way.
How can I define the capabilities for chrome driver only? |
Solved by myself when removing the capability "browserName=chrome". |
@abergmeister could you please tell me where i need to put the above?? local { |
see https://serenity-bdd.github.io/docs/guide/driver_config#configuring-chromedriver-arguments
|
@globalworming I have added that but not working for me |
remove the |
@globalworming removed the dots but still the same
|
you messed up the format somewhere |
Dear Serenity Devs.
With the update of chrome browser and chrome driver to version 111 a critical communication issue has been started:
According to the thread on groups.google this issue seems to be caused by selenium itself. The workaround mentioned is to apply the chrome option "--remote-allow-origins=*".
Unfortunately, I cannot apply this switch in "serenity.conf" correctly i.e. the error is still shown. The below was not working:
Why is the above switch not working as expected? Please, help to solve this critical issue.
Thanks and best regards, André
The text was updated successfully, but these errors were encountered: