UPDATED: Feb 26 2018 (later that day)
This post is a follow up to how I got Xamarin Android Device Manager up and running on Windows. Please read the Xamarin Developer guide first which explains how to install and use the Xamarin Android Device Manager for Visual Studio on Windows (or for Mac). Please keep in mind that at the time of this post the Xamarin Android Device Manager is still in preview.
For me I’m running the latest version of Visual Studio 2017 (15.5.7) and I already had the Xamarin components installed and working. Up until now I wasn’t really using the Android emulators for any Xamarin development as I was more focused on iOS and Windows. However now I have a need to and so I decided to try out the new Xamarin Android Device manager. Why you might ask? Well as of Android SDK Tools version 26.0.1, Google has removed support for their UI-based AVD and SDK managers in favor of their new CLI (Command Line Interface) tools.
After having installed the latest version of the Xamarin Device Manager installer for Windows, I ran it from the Start menu with Administrator privileges like so:
And this is the error I get:
I ran through the troubleshooting section section and the issue is that I was missing the Android SDK (requires 26 or higher). Perhaps a one of the latest Visual Studio updates caused this issue because now none of the Android tooling like device or emulator are working. Perhaps installing the Xamarin Device Manager broke it, I’m not sure but it’s broken. The only way I was able to resolve this was to run the Visual Studio Installer and uninstalled the the Xamarin SDK Manager and re-install it. Here is what I did.
My Solution to Fixing Missing Android SDK
1. Run Visual Studio Installer and then click on the Modify button:
2. Now go to the Individual components tab and Remove Xamarin SDK Manager and then click on the Modify button to apply the changes. Take notice of the amount of disk space that will be freed up. For me it was 113 MB.
3. Now do steps 1 and 2 again but this time add back the Xamarin SDK Manager and then notice the amount of disk space required for these changes…for me it was 1.4 GB, obviously something screwed up and I was missing a great deal. Now apply the changes by clicking on the Modify button.
Now when you run the Xamarin Android Device Manager from the start menu (with administrator rights) it should load up as expected. Now if you are like me and don’t have the latest Android SDK Tools, then you are then presented with the following dialog prompting you to download them from the Xamarin Android SDKs and Tools manager:
When the Xamarin Android SDK and Tools manager opens, review the SDK platforms you want installed and then click over to the Tools tab:
In the Tools tab, expand the Android SDK Tools selection and change the selected tooling to the current version which is 26.1.1 and then click on the Apply Changes button. If you’re just changing the Android SDK Tools, this should only take a couple min at most to apply. Once it’s done close down the Android SDKs and Tools manager.
Now go back to Visual Studio (re-run if you have it running already) and run the Android Emulator Manager from the Tools – > Android menu.
You will now be presented with the new Android Devices manager. When you first launch the Android Device Manager, it presents a screen that displays all currently configured virtual devices. For each device, the Name, Operating System (Android API Level), CPU, Memory size, and screen resolution are displayed:
I then went on and added a new option for Android Oreo and when I tried to run it I got another error:
Now it looks like I need to install another tool, Intel’s HAXM which requires Hyper-V be disabled.
What seemed like a quick and easy update has turned into quite the adventure. It’s 2018…why can’t this be more simple!