I had to do a lot of fine tuning and customization for those Android Virtual Devices. So recently I got a little deep into the new Xamarin Android Emulator set up in Visual Studio 2019, where I had to build a whole bunch of custom Emulators for some experiments. Yeah seriously I hated that and had a lot of issues using those emulators. Microsoft had finally rolled out a full fledged Android Emulator set up (Xamarin Android Device Manager) that’s very stable and much easier to use with Xamarin mobile development, expiring the previously buggy always-out-dated VS Emulator set up that was shipped for Xamarin dev. It worked for me.Let me share some of my experience with playing around with the latest updated Android Emulators in Visual Studio 2019! \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools\PathĬhange the path to match the Android Studio SDK path, close everything, start the VS Emulator, run Android Studio, ensure ADB integration is off and try. We then decided to use Xamarin for our projects, so Xamarin was installed and installed an additional SDK by default, located here: C:\Program Files (x86)\Android\android-sdk.Ĭhanging Xamarin to match the same SDK path worked for me which I did in the registry (although through the VS settings I'd guess it's the same):
My case may be different to others but I had Android Studio installed first which installs the SDK by default to: C:\Users\\AppData\Local\Android\sdk. This thread helped me to solve my problem, in particular this answer:įor anyone else having the issue - none of the answers provided worked for me. If your case is different then restart your Android Studio and run the emulator again. You should also uncheck Tools > Android > Enable ADB Integration Check in your adle file if the targetSDK and minimumSdk version is lower or equal to the sdk version of your Emulator.
Probably the project you are running is not compatible (API version/Hardware requirements) with the emulator settings.
0 kommentar(er)
