ERR_NON_ZERO_EXIT: Non-zero exit code from Emulator: 1

[imhoffd]

This is an unhelpful error message and requires --verbose to uncover the cause.

Additionally, when it occurs the native-run process continues running despite encountering a fatal error. This is because waitForDevice is called beforehand, which spawns an adb process that will never complete.

[untilbit]

I get this issue a lot

[AlameerAshraf]

Any updates regarding this issue.

[CubKAI]

You can try trun off hyper-v

[AlameerAshraf]

I found out the problem was from my device as the device has not enough space to install the new app, so I'm recommending using Android studio profiler and debugger to get the real error message.

[imhoffd]

As a reminder, that's what this issue is for: to uncover the reasons behind the vague error message. As always, dissecting the output with the --verbose flag can reveal more information.

[SchnWalter]

I think that we can close this in favor of #89

Maybe someone has an idea on how to parse the known adb error messages. I've tried looking for the adb source code, but had no luck.

[imhoffd]

@SchnWalter We also boot up the emulator process which has its own issues separate from adb.

This particular issue is for adding better error handling with the emulator process, and uncovering more details from emulator output, which is on average less helpful than adb output.

The existing code for this is here:

native-run/src/android/utils/emulator.ts

Lines 112 to 118 in 9b87583

	if (line.includes('Unknown AVD name')) {
	event = EmulatorEvent.UnknownAVD;
	} else if (line.includes('another emulator instance running with the current AVD')) {
	event = EmulatorEvent.AlreadyRunning;
	} else if (line.includes('Cannot find AVD system path')) {
	event = EmulatorEvent.AVDHomeNotFound;
	}

[jakoblylu]

Also get this error alot