Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 5604 [details]
Example screen grab of before and after second device attached
Description of Problem:
If a second Android Android device is connected (via USB) the XS loses some connection information on one of the Devices and either, or both devices, cannot then be debugged. I have a Nexus 7 and HTC Desire, each of which can be debugged if only one is connected at a time.
Steps to reproduce the problem:
1. Connect an Android Device to USB (I use Google Nexus 7)
2. Connect second Android Device to USB (I use HTC Desire)
(I would suggest that you may have to restart XS between each operation)
First Android Device details lost in the XS
I would expect BOTH Android Devices to be fully recognized, and potentially debuggable
How often does this happen?
Every time I connect two Android devices to two USB ports
You will notice from the screen grab that the Google Nexus 7 (05865C1) becomes Android Device (058651c1), and as an 'Android Device' it cannot be debugged.
I suspect that this situation occurs with earlier XS versions.
Can you please attach the AndroidTools log for this session? You can find long files in Help -> Open Log Directory.
This may be an issue in adb, all I can tell from the logs is that we're losing the TCP connection to adb.
Is there any specific pattern to when it happens?
@Tony, are you able to tell me if this is an ongoing issue for you? We have made many different changes to handle ADB vagaries and I've not ever been able to reproduce this particular one.
If this is still an issue, please reopen the bug with as much information as you can provide, including the AndroidTools log from Help | Open Log Directory.