chromedriver fails to start sometimes because of adb returns wrong device name

Sending adb command: host:devices\n[0.033][DEBUG]: Received adb response: 0015emulator-5554\tdevice\n\n[0.033][INFO]: RESPONSE InitSession unknown error: Device emulator-5554 is not online\n[0.033][DEBUG]: Log type \'driver\' lost 0 entries on destruction\n[0.033][DEBUG]: Log type \'browser\' lost 0 entries on destruction\n[0.246][INFO]: COMMAND InitSession {\n "desiredCapabilities": {\n "chromeOptions": {\n "androidDeviceSerial": "emulator-5554",\n "androidPackage": "io.selendroid.testapp",\n "androidUseRunningApp": true ^^ above adb returns extra 0015emulator-5554\tdevice\n which is causing test to fail.

Chromedriver/appium should be able to retry without device name.

cc @filmaj

[PeaceDeveloper]

I installed the windows appium via executable. And to me also happened the same problem reported by the noble colleague.

I solved it this way:

1. First I accessed the folder C:\Program Files (x86)\Appium\node_modules\ appium.
2. I drove the ncu -u. With that all packages will be upgraded to the latest version. I did not notice any side effects with this act.
3. After that, everything started to work in the best possible way.

I hope I have helped someone. 😃

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.