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 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.
After VS succesfully connects to the build host, sometime (70% chance) the dropdown list stays empty.
If you wait a minute or two, it may fill (or not).
If it does not fill, most of the time, a simple workaround is to kill the mac service IDB.exe (one or multiple times) until this dropdown list fills by itself.
If this workaround does not work, closing visual studio, waiting for all Xamarin mac services to shutdown (ps -eax | grep Xamarin), and restarting VS also fix the issue.
Last option: reboot the mac and the pc.
This also happens when the pc wakes up, after it went to sleep.
## Note to the Xamarin engineering team
At first glance it appears this issue might have the same underlying cause as Bug 37613 (Bug 38695).
We couldn't reproduce this issue so I'll change it to resolved.
If you're still able to reproduce it with the latest beta version (4.1), please reopen this bug.
I am also no longer able to reproduce this issue. I am getting drop-down list of simulator and real devices properly.
So as of now I am closing this issue. If anyone face this issue so feel free to reopen it or file a seperate issue.
This still happens fairly often, after connecting the simulator list does not populate.
This exact bug report can be considered closed at this time since (a) it has been marked as resolved for a bit over 9 months, (b) the fixes for the bugs mentioned in Comment 1 might have resolved a number of the precise symptoms as originally reported in Comment 0, and (c) there have been many code changes since the original report. For any appearances of similar issues in more recent version, please file new bug reports and be sure to include as many details  as possible. A new bug report will have the added advantage that the discussion can focus on the issue as experienced by the most recent user hitting the issue. Thanks in advance!