Replies: 6 comments 10 replies
-
Currently the screenshot shows all emulators collected from all nodes, As the udid are same across for emulators which may not be for real devices thats the reason we are adding node IP so its easy to identify the device. We can also add another feature as node name which the user can provide and we can add that as well for easy identification. Thoughts ? |
Beta Was this translation helpful? Give feedback.
-
@saikrishna321 The problem is not so much in identification, but in the start of the driver, we only get to driver udid device in capabilities, will device-farm be able to manage sessions correctly to another emulators, but with the same udid? |
Beta Was this translation helpful? Give feedback.
-
What is the problem now? We are handling it correctly when it comes to hub n node config thats the scenario when emulator will have same udid. |
Beta Was this translation helpful? Give feedback.
-
@saikrishna321 If I specify the judid emulator-5554, does the server select the first smallest by $loki device? |
Beta Was this translation helpful? Give feedback.
-
Yes, it will pick the first free device matching the udid from one of the nodes and run the test. |
Beta Was this translation helpful? Give feedback.
-
I have issue related to Jenkin also. |
Beta Was this translation helpful? Give feedback.
-
@saikrishna321
Android Studio and Genymotion can add on another PCs only same udids like on screenshot, can we do something to unify them/perceive them somehow differently so that you can interact with them normally
My task is that I need to collect all available emulators from all nodes
Beta Was this translation helpful? Give feedback.
All reactions