-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
Devices listing bug #48
Comments
Hey, thank you :) |
Commonly, this case happens when user runs "adb" commands from terminal and from dexcalibur. Since Dexcalibur come with own ADB binary, when dexcalibur executes ADB command, it must restart daemon. |
The strange behaviour is that before this happen Dexcaliur correctly launched the "adb kill" command, and so, I am expecting that id already restarted it's correct server, but anyway it tries to restart adb server also when you launch the device listing command |
Hello,
sometimes Dexcalibur shows Devices ID with a simple "*".
This means that it doesn't correct recognized the device, simply because it launched the adb devices listing command, that returned a string like "* daemon started successfully *" and it get the first character as a correct Device ID.
To let it works with a workaround, I modified that piece of code to call device listing two times, in this way:
Hope it helps other guys and developers
The text was updated successfully, but these errors were encountered: