I am getting this error when trying to launch the ...

# android

[Utkarsh Tiwari]

I am getting this error when trying to launch the emulator

The emulator process for AVD Pixel_2_API_27_Phone_ was killed.

Does anyone know what could be causing this issue?

[Utkarsh Tiwari]

Screen Shot 2021-03-11 at 10.28.10 AM.png

[allan.conda]

lots of emulator crashes recently
https://issuetracker.google.com/issues?q=emulator%20crash
API 26 device works for me

[Utkarsh Tiwari]

26 doesn’t work for me either.

[goku]

What is your MacOS version (if you are on Mac)?

[Utkarsh Tiwari]

10.14.6 (macOS Mojave)

[goku]

Nothing worked for me except upgrading to latest, I shared my findings in this answer: https://stackoverflow.com/a/66422209/1106598

[Utkarsh Tiwari]

I didn’t upgrade mac for last 3 months, I didn’t update AS too, I think. It started behaving like this all of sudden.

[Utkarsh Tiwari]

Nothing worked for me except upgrading to latest, I shared my findings in this answer:

Let me try that

[goku]

Same for me. I was on 10.14 Mojave. I didn't even upgrade my Android Studio and this happened. My guess, they changed something in latest emulator that looks for a certain package in MacOS. Apple moved some of their packages in latest version. But emulator update didn't account for old MacOS versions. This is just my assumption, not a verified info

[Umar Ata]

Actually from Mojave something like permission is added in MacOS applications and emulator does not have that
So we need to provide it separately,
Goto Users/username/.android/avd/emulator-folder/ now check file encryptionkey.img
Provide this file read/write/execute permission and see if it works
This answer is based on my understanding and the problem I faced months ago, not sure if it works in yours

[Utkarsh Tiwari]

It doesn’t have any encryptionkey.img. Maybe that’s the reason.

[Utkarsh Tiwari]

I guess, I’ll have to take the leap of faith which I have been avoiding for so long blob sweat smile

[Umar Ata]

Can you create a new emulator

[Umar Ata]

Select pixel 4 or 3 or even 2
Pixel C is quite old to use

[Utkarsh Tiwari]

I tried Pixel 2. 4 and C both. Same error 😢

[Umar Ata]

What OS you selected for emulator

[Utkarsh Tiwari]

Screen Shot 2021-03-11 at 12.25.11 PM.png

[Umar Ata]

It must have that encryption image, check it

[Utkarsh Tiwari]

It doesn’t. None of them have that .img

[Umar Ata]

provide read/write/execute permission to the emulator folder and see if it works

[Utkarsh Tiwari]

Did that, doesn’t work.

[Utkarsh Tiwari]

Apparently lot of people facing same issue:
https://issuetracker.google.com/issues?q=AVD%20was%20killed

[Utkarsh Tiwari]

@Umar Ata Thanks for your efforts. Let me try the new update. Hopefully BigSur can save us.

[Umar Ata]

how you provided the permission to that folder

[Utkarsh Tiwari]

Screen Shot 2021-03-11 at 12.52.05 PM.png

[Umar Ata]

ls -la

[Umar Ata]

to show what permission to that folders

[Utkarsh Tiwari]

Screen Shot 2021-03-11 at 12.53.28 PM.png

[Umar Ata]

cd ..
sudo chmod 775 avd

[Utkarsh Tiwari]

Screen Shot 2021-03-11 at 12.56.28 PM.png

[Utkarsh Tiwari]

Doesn’t work

[Umar Ata]

Now create new emulator

[Utkarsh Tiwari]

Doesn’t work. I respect your tenacity 🙇

[goku]

Just upgrade it, trust me. It was the only thing that worked for me 🙂 I spent 2 days on this. Adding, deleting emulators, AS, clearing caches.. I even found older versions of emulators and installed them manually but couldn't trick AS into accepting it.

[Utkarsh Tiwari]

Thank you so much Gokhan! Updating to BigSur fixed the issue 🙇