Open bhecquet opened 2 days ago
@bhecquet, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
Good catch. Would you like to send a PR to fix this?
Yes sûre If you agree, I will just remove browserName cap in case appium:app is present, hoping there is no other incompatibility
That approach sounds good.
What happened?
Hello,
I've set up a selenium grid with an appium server which is linked to grid through relay feature
the android device stereotype is:
When I want to test a mobile application, I provide the following capabilities
But, the received capabilities on appium side are:
This is due to https://github.com/SeleniumHQ/selenium/blob/54941080765f976b88da7f273f1647b2d98aaf70/java/src/org/openqa/selenium/grid/node/relay/RelaySessionFactory.java#L149
which merges stereotypes from slot (where 'browserName' is present) and requested capabilities (where 'appium:app' is present) According to UIAutomator2 driver,
Do not provide both app and browserName capabilities at once.
This change has been introduced with this commit: https://github.com/SeleniumHQ/selenium/commit/0013140fd587310ad38cffef9150bd8fc96b89ed
I think one of the solution would be to make de "merge" operation more precise (e.g: not adding browserName if appium:app is provided). This would add some specific code whereas relay session is generic, but it's a common use case If you have any other idea, I would be glad to implement a correction
Bertrand
How can we reproduce the issue?
Relevant log output
Operating System
Any
Selenium version
4.18.1
What are the browser(s) and version(s) where you see this issue?
Chrome / not related to browser
What are the browser driver(s) and version(s) where you see this issue?
not related to browser
Are you using Selenium Grid?
4.18.1