Closed dorsegal closed 8 months ago
But it looks like emulator didnt crash. It was fully booted according to you screenshot and moved to next step which is launching appium.
So i would ask you to remove the restart option and see how it will behave.
I was a simulating a crash right after appium was starting.
But it looks like emulator didnt crash. It was fully booted according to you screenshot and moved to next step which is launching appium
Try to run the command manually and see the output
The way I simulated a crash:
The way I simulated a crash:
- docker exec -it android bash
- apt update && apt install -y procps
- ps aux
- kill -9 {emulator PID}
Try aslo to kill the adb server, before starting the emulator after being crashed
I found the issue. After checking emulator logs I see this error: Running multiple emulators with the same AVD is an experimental feature.
the solution I did was adding this line to start_emu_headless.sh
:
rm ~/.android/avd/*.avd/*.lock
I found the issue. After checking emulator logs I see this error:
Running multiple emulators with the same AVD is an experimental feature.
the solution I did was adding this line to
start_emu_headless.sh
:rm ~/.android/avd/*.avd/*.lock
Awesome Gald that you have solved it.
I think also killing adb server will eliminate the first one so you wont have problem running another with same name.
I am running using docker-compose.yaml and I have added
restart: unless-stopped
option so it will restart in case something happens. When there is a crash for whatever reason container is being restarted but emulator can't start. it is just hangs till timeoutmy docker-compose: