You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
On the right hand side you see that the Android Emulator is still running. I had to cold boot of my computer while it was running an emulator. The emulator is no longer running but Nuclide thinks it is.
Expected Behavior
I expect it to check whether Android Emulator is actually running.
Actual Behavior
Nuclide is not checking to see if Android Emulator is running and does not allow me to start it.
Versions
Atom: 1.24.0
Electron: 1.6.16
Chrome: 56.0.2924.87
Node: 7.4.0
Nuclide: 0.288.0
Client OS: Ubuntu 16.04.4 LTS
The text was updated successfully, but these errors were encountered:
This nuclide version is quite old, are you running it as a workaround for #1576?
Otherwise I suggest updating Nuclide/atom and see if it still reproduces.
I've familiar with this issue and it hasn't been fixed.
The problem here is that the devices panel checks for the lock file for each emulator and if it exists it assumes it's running. This is not a reliable assumption because the lock file will not be removed when the emulator is forced killed. @csellis a quick workaround is to remove the lock file from ~/.android/avd/$DEVICE.avd/hardware-qemu.ini.lock.
On Wed, Jul 25, 2018, 4:39 PM António Afonso ***@***.***> wrote:
I've familiar with this issue and it hasn't been fixed.
The problem here is that the devices panel checks for the lock file for
each emulator and if it exists it assumes it's running. This is not a
reliable assumption because the lock file will not be removed when the
emulator is forced killed.
@csellis <https://github.com/csellis> a quick workaround is to remove the
lock file from ~/.android/avd/$DEVICE.avd/hardware-qemu.ini.lock.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1580 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAxtRe0WfGZCrCgU4Lg_kA7PcbuyYNnwks5uKNeWgaJpZM4Vga7t>
.
Issue and Steps to Reproduce
On the right hand side you see that the Android Emulator is still running. I had to cold boot of my computer while it was running an emulator. The emulator is no longer running but Nuclide thinks it is.
Expected Behavior
I expect it to check whether Android Emulator is actually running.
Actual Behavior
Nuclide is not checking to see if Android Emulator is running and does not allow me to start it.
Versions
The text was updated successfully, but these errors were encountered: