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
I have tested this issue on the latest Detox release and it still reproduces.
Did your test fail and you're not sure why?
I have read the troubleshooting guide and it didn't help me.
What happened?
Running detox test --configuration android.emu.debug fails with correct emulator name with error message:
DetoxRuntimeError: Cannot boot Android Emulator with the name: 'a15'
,w14r Make sure you choose one of the available emulators: A9
Running emulator list returning this device, so it's not an issue with missing device:
>emulator -list-avds
A9
a15
w14r
Since issue is reproducing only on Windows machine, I assume it's related to AVDResolver using LF instead of CRLF for splitting device names
What was the expected behaviour?
Expected to work with device in place and all environment variables set up
Help us reproduce this issue!
To avoid issue quick fix should work:
const { ListAVDsCommand } = require('../../../../common/drivers/android/emulator/exec/EmulatorExec');
const { EOL } = require('os');
class AVDsResolver {
constructor(emulatorExec) {
this._emulatorExec = emulatorExec;
}
async resolve() {
const output = await this._emulatorExec.exec(new ListAVDsCommand());
const avds = output.trim().split(EOL); // Using OS native end of line to split emulators list
return avds;
}
}
module.exports = AVDsResolver;
In what environment did this happen?
Detox version: "^20.39.0"
Test-runner (select one): jest
Detox logs
Detox logs
● Test suite failed to run
,w14rRuntimeError: avds:A9
HINT: avdName:a15
at AVDValidator._assertAVDMatch (node_modules/detox/src/devices/allocation/drivers/android/emulator/AVDValidator.js:38:13)
at AVDValidator.validate (node_modules/detox/src/devices/allocation/drivers/android/emulator/AVDValidator.js:18:16)
at async EmulatorAllocDriver.allocate (node_modules/detox/src/devices/allocation/drivers/android/emulator/EmulatorAllocDriver.js:59:5)
at async C:/Projects/PROJECT_NAME/node_modules/detox/src/devices/allocation/DeviceAllocator.js:44:22
Device logs
Device logs
paste your device.log here!
More data, please!
No response
The text was updated successfully, but these errors were encountered:
The solution proposed above manages to launch the emulator, but still fails tests because it can't connect to the emulator (perhaps due to console errors when launching the emulator, and tries to restart the emulator for each test).
Did you test using the latest Detox?
Did your test fail and you're not sure why?
What happened?
Running
detox test --configuration android.emu.debug
fails with correct emulator name with error message:Running emulator list returning this device, so it's not an issue with missing device:
Since issue is reproducing only on Windows machine, I assume it's related to AVDResolver using LF instead of CRLF for splitting device names
What was the expected behaviour?
Expected to work with device in place and all environment variables set up
Help us reproduce this issue!
To avoid issue quick fix should work:
In what environment did this happen?
Detox version: "^20.39.0"
Test-runner (select one): jest
Detox logs
Detox logs
Device logs
Device logs
More data, please!
No response
The text was updated successfully, but these errors were encountered: