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.
The target android device drop down doesn't refresh predictably and I can't get the emulator to show up there since upgrading to the new xamarin studio version in VS2012.
The devices will show up when trying to debug and left to prompt, but then don't populate the device selection menu meaning the device must be selected every time.
Also, when a physical device is connected, it shows up but when selected it says "Value does not fall within the expected range."
In Xamarin.Android v220.127.116.11, I have the same issue.
1. Load an Android project
2. Create new emulator in AVD Manager
3. Return to Visual Studio and check device drop-down list in the Xamarin toolbar
The new emulator should show in the toolbar device list so you can select it going forward.
The new emulator will not show.
Closing/Re-opening the project will not refresh the list.
Refreshing in AVD Manager will not refresh the list in VS.
The only way I could get it to refresh was to restart Visual Studio entirely; then it would show up in the list.
I have checked this issue, I am not seeing this Issue. This is the screencast for the same: http://www.screencast.com/t/Hxk2JuDR7
XVS 3.9.230(Xamarin.Android 18.104.22.168)
Are you still observing this Issue with latest build?
I have checked this issue with latest stable XVS 3.11.666 and able to reproduce above behavior given in the bug description.
Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Installed Version: Professional
Xamarin 3.11.666.0 (ebae43a)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 22.214.171.124 (5f55a9ef61c11b6ce0890bc91e4c71b1b92be214)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.Forms Intellisense 1.0
Provides intellisense for Xamarin.Forms in the XML editor.
Xamarin.iOS 126.96.36.199 (67b390d0d1bd741582cf7b7fd3ffea08583a3f83)
Visual Studio extension to enable development for Xamarin.iOS.
Xamarin.iOS Unified Migration 1.0
Automated migration for Xamarin iOS Classic projects to Unified
Early preview of Xamarin Test Cloud integration
Created attachment 12043 [details]
Zip Xamarin Logs