-
-
Notifications
You must be signed in to change notification settings - Fork 764
chore: Bump minimum selenium api version to 4.2.0 #1696
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
Conversation
The failing iOS test is a legitimate xcuitest driver bug: appium/appium#17003 |
@SrinivasanTarget Could you please publish 8.1.0 when you have time? |
Sure |
@SrinivasanTarget I'm facing the "AcceptedW3CCapabilityKeys" issues, can you please publish an update soon? Thank you for everything. |
Yes will release it today |
java.lang.NoClassDefFoundError: org/openqa/selenium/remote/AcceptedW3CCapabilityKeys
Caused by: java.lang.ClassNotFoundException: org.openqa.selenium.remote.AcceptedW3CCapabilityKeys Is it related to issue? |
I'm still getting error |
the update from this PR is not released yet, please, read comments above carefully |
Java client 8.1.0 is released and should be live in mvn repository in a few minutes :) |
@SrinivasanTarget , It is not updated in maven repo. Please find screenshot |
@Ayush-17 weird, I will have a look at it soon. Thanks for letting me know. |
@Ayush-17 actually everything is in place: https://repo1.maven.org/maven2/io/appium/java-client/8.1.0/ . I can confirm the release build can be retrieved successfully |
it's normal, the search engine always is late with indexing the fresh artifacts. Version 8.1.0 will appear in search result with some delay, but you can already use this dependency in your build scripts. |
Types of changes