Menu
I recently installed VS 2017. Trying to run a blank Android App Project. All necessary tools are installed but when I try to launch the emulator from within Visual Studio, I get this:
Any Help will be greatly appreciated.
553
The Visual Studio Emulator for Android was created as a replacement for the Google AVD when the Google emulators were limited to ARM images which ran excruciatingly slow. For some time Google have provided Intel images which, alongside the HAXM driver, run as fast as (if not faster) than the Visual Studio Emulator for Android.
So, it is always a good option to create the emulators from the Visual Studio (Xamarin tools for Android). Last but not least, try to check the logs and see what exactly is causing the problem. In most cases, it might be that there is a mismatch in the SDK, or the emulator needs to be updated.
Note:After we released the Visual Studio Emulator for Android, Google updated their Android emulator to use hardware acceleration. We recommend you use Google’s emulator when you can, as it offers access to the latest Android OS images and Google Play services.
One thing that I have noticed in my experience with Xamarin (I assume you are using Xamarin to develop Android application), that Android Studio emulators do not work—because the Android SDKs that you download from Android Studio sometimes do not match the Visual Studio ones.
I am having the same problem too. I am able to run the Hyper-V emulators in VS 2015 but not VS 2017. When I try to launch them in VS 2017 I receive Object reference not set to an instance of an object.
If the emulator is already running I am able to run the app that I'm working on from VS 2017. So to work around this I start the emulator from Visual Studio Emulator for Android Windows application and then launch the app that I'm working on from VS 2017. Not great, but it works.
By the way, the Windows Phone 10 Hyper-V emulators launch without issue from VS 2017.
Update
I just installed the latest VS 2017 (on April 8) update and the problem appears to have been corrected.
170
Perhaps Android SDK didn't install/update properly. You can try reinstalling Android SDK.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
