CRM & Cloud

Issues I faced in CRM & Cloud solutions

Xamarin Android > PANIC: Missing emulator engine program for 'x86' CPU

I updated my Adroid SDK and right after that everything stops working and I started getting error message "PANIC: Missing emulator engine program for 'x86' CPU".

I started looking into this issue and found that on the Visual Studio output following command was being set:

C:\Program Files (x86)\Android\android-sdk\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd Android_Accelerated_x86_Oreo -prop monodroid.avdname=Android_Accelerated_x86_Oreo
while my path to the emulator when i checked is:
C:\"Program Files (x86)\Android\android-sdk\emulator.EXE
 Further I noticed that when I tried to run emulator from command line from path "C:\"Program Files (x86)\Android\android-sdk\emulator.EXE" the emulator was getting started but from path "C:\Program Files (x86)\Android\android-sdk\tools\emulator.EXE" it was giving the same error message PANIC..

So until here i understood the issue that what is the problem I was dealing with, only thing i had to do was to point my visual studio to start new emulator instead of the older one.

When i googled visual studio forum to check the fix for this issue then i found that it is a known bug and it is going to be fixed in release 15.8 while current release is 15.7.6.

This is what Microsoft official replied:

Added a solution by Jon Douglas [MSFT] Thank you for your feedback! We have fixed this issue and it's available in a future version of Visual Studio. This issue came down to our IDEs using the old outdated tools/emulator path when Google moved emulator items in 25.0.3 to emulator/emulator instead. We have updated this path and thus consider this behavior fixed. Expect this to be inside a 15.8 proper release and we will work on trying to get it in a 15.7 SR if possible.
Question 
URL: https://developercommunity.visualstudio.com/content/problem/252854/unable-to-start-android-emulator-from-within-visua.html
So after getting to know there is not proper fix so I started to look into workarounds..
The workaround I found is very simple, please follow below steps:
  • Go to "Open Android Device Manager"
  • Delete the existing Device
  • Create a New device and MUST select "Google Play Store"
  • Click "Create"




No comments:

Post a Comment