You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the idea behind this? The method name is misleading without any context. Have I misunderstood something in trying to get to the bottom of things?
Note that I just switched emulators and the new one uses port 7555 instead of 5555. I did not have this issue with the old emulator - maybe it ran adb connect itself?
Any feedback is appreciated. I was not able to find a way to run adb connect before using connectToDeviceOrExit after reading the wiki and API docs. This leaves me thinking that this library is not right for me since my use case is simple.
Edit: it seems like maybe this usage falls under "remote" devices, so this issue might be specific to that
The text was updated successfully, but these errors were encountered:
aentwist
changed the title
ViewClient.connectToDeviceOrExit does not connect to devices, it only lists devices that are already connected and uses themViewClient.connectToDeviceOrExit does not connect to (remote?) devices, it only lists devices that are already connected and uses them
Aug 9, 2024
The only connecting AdbClient does is to the adb server, not any devices
AndroidViewClient/src/com/dtmilano/android/adb/adbclient.py
Line 267 in 8738d3a
Then after not doing any connecting to devices, they are listed
AndroidViewClient/src/com/dtmilano/android/adb/adbclient.py
Lines 471 to 473 in 8738d3a
This results in a blank list and failure
When I actually connect
Only then do I find immediate success with
connectToDeviceOrExit
What is the idea behind this? The method name is misleading without any context. Have I misunderstood something in trying to get to the bottom of things?
Note that I just switched emulators and the new one uses port 7555 instead of 5555. I did not have this issue with the old emulator - maybe it ran
adb connect
itself?Any feedback is appreciated. I was not able to find a way to run
adb connect
before usingconnectToDeviceOrExit
after reading the wiki and API docs. This leaves me thinking that this library is not right for me since my use case is simple.Edit: it seems like maybe this usage falls under "remote" devices, so this issue might be specific to that
The text was updated successfully, but these errors were encountered: