[🐛 Bug]: Cannot start mobile application with appium when slot also specifies a 'browserName' capability about selenium HOT 7 CLOSED

@bhecquet, thank you for creating this issue. We will troubleshoot it as soon as we can.

from selenium.

Good catch. Would you like to send a PR to fix this?

from selenium.

Yes sûre
If you agree, I will just remove browserName cap in case appium:app is present, hoping there is no other incompatibility

from selenium.

That approach sounds good.

from selenium.

this can fix this issue too:

boolean browserNameMatch = (stereotype.getBrowserName() == null || stereotype.getBrowserName().isEmpty() || capabilities.getBrowserName() == null || capabilities.getBrowserName().isEmpty()) || Objects.equals(stereotype.getBrowserName(), capabilities.getBrowserName()); boolean browserVersionMatch = (stereotype.getBrowserVersion() == null || stereotype.getBrowserVersion().isEmpty() || capabilities.getBrowserVersion() == null || capabilities.getBrowserVersion().isEmpty()) || Objects.equals(stereotype.getBrowserVersion(), capabilities.getBrowserVersion());

from selenium.

@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).
Problem is on session creation, after matching

I've written a correction that I need to verify before creating the PR

from selenium.

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.

from selenium.