Device conflict while running Appium test using selenium grid

Support
21

Thanks for your anwser @afwang, with that anwser you provided already fixed all my issues in my grid and I could put my two capabilities (serial and browserVersion) running at same time.

One more time my thanks :relaxed:

22

Watch: https://youtu.be/vXpskMkytD8

23

Hi I am facing the same issue still. Please do help me out in understanding what is the reason. The hub is assigning the nodes randomly and is not honoring the udid sent as capability.

Capabilities sent -
app: path, appActivity: startupActivity, appPackage: package, autoGrantPermissions: true, automationName: uiautomator2, deviceName: ZY223V2RNW, newCommandTimeout: 45000, platformName: android, platformVersion: test-7.0, udid: ZY223V2RNW

Hub assigning the node -
Trying to create a new session on test slot {seleniumProtocol=WebDriver, se:CONFIG_UUID=ae14c80e-0632-4320-8435-7cb16b16a1b7, browserName=chrome, maxInstances=3, platformName=ANDROID, deviceName=ZY2244JGLL, version=7.0, platform=ANDROID}

If observed the node assigned and the device details sent are totally different

Command to start the node -
appium --address localhost -cp 9966 --port 4630 -bp 8555 --default-capabilities ‘{“udid”:“ZY223V2RNW”,“device-name”:“ZY223V2RNW”, “platform-version”:“test-7.0”}’ --nodeconfig pathOfConfig

Node config json

{
“capabilities”:
[
{
“deviceName”:“ZY223V2RNW”,
“browserName”: “chrome”,
“version”:“test-7.0”,
“maxInstances”: 3,
“platform”:“Android”,
“seleniumProtocol”:“WebDriver”

    }
  ],

“configuration”:
{
“cleanUpCycle”:240,
“timeout”:240,
“proxy”: “org.openqa.grid.selenium.proxy.DefaultRemoteProxy”,
“url”:“http://localhost:4444/wd/hub”,
“host”: “localhost”,
“port”: 4630,
“role”:“node”,
“maxSession”: 3,
“register”: true,
“registerCycle”: 5000,
“hubPort”: 4444,
“hubHost”: “localhost”,
“unregisterIfStillDownAfter”:60000,
“downPollingLimit”:2,
“nodeStatusCheckTimeout”:5000,
“nodePolling”:5000
}
}