-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[🐛 Bug]: Cannot start mobile application with appium when slot also specifies a 'browserName' capability #14216
Comments
@bhecquet, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Good catch. Would you like to send a PR to fix this? |
Yes sûre |
That approach sounds good. |
this can fix this issue too:
|
@krishtoautomate , I don't thinks so, as you suggest a change in Matcher whereas matching is correctly done on my side (I've not checked if it's due to my custom matcher or not). I've written a correction that I need to verify before creating the PR |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
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
selenium/java/src/org/openqa/selenium/grid/node/relay/RelaySessionFactory.java
Line 149 in 5494108
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: 0013140
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
The text was updated successfully, but these errors were encountered: