-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
java-client's NewSessionPayload.class conflict with selenium's NewSessionPayload.class #875
Comments
Hi @SrinivasanTarget , @TikhomirovSergey , |
@Trucnt |
@Tenit2012 The reply above is for you too. |
Hi @TikhomirovSergey My problem is when I run with Firefox driver, ProtocalHandShake.java class of library selenium called NewsessionPayload.java class of java-client library instead call NewsessionPayload.java class of selenium library. I want to run with Firefox driver, ProtocalHandShake.java class will call NewsessionPayload.java of selenium library. Because both selenium and the Appium java-client contains org.openqa.selenium.remote.NewsessionPayload.java. Did you reproduce on my issue? |
Is it indeed an Appium java client issue, @TikhomirovSergey ? |
Guys. I am investigating |
Guys @Trucnt @Tenit2012 It is normal now that NewsessionPayload from appium is used instead of the same class from selenium. It was the necessary step and we hope the situation will be changed. Also the appium lib has all dependencies from selenium. Could you remove the dependency on selenium java and add such exclusion to selenium-server dependency? What the result? |
Hey @TikhomirovSergey , As your suggestion, I have removed both selenium-java and selenium-server but this issue still happens. To reproduce this problem, You must create FirefoxDriver with FirefoxOptions and FirefoxProfile is set into FirefoxOptions. Further detail, please see screenshot below: Please let me know if any update. Thanks in advance. |
@Tenit2012 Ok. Trying to work it out. Thank you for details |
Yes. I could reproduce this error. It seems something was broken because we did not test it on desktop browser. |
The fix was merged. It is going to be published soon. |
OS: Windows 10
Selenium Version: 3.9.1
Browser: Firefox
Browser Version: 59.0.2 (64-bit)
Expected Behavior
Actual Behavior
Exception in thread "main" org.openqa.selenium.InvalidArgumentException: firefox_profile is not the name of a known capability or extension capability
Steps to reproduce
------------------------------------------pom.xml file------------------------------------------------------
The text was updated successfully, but these errors were encountered: