[Error: An unknown server-side error occurred while processing the command. (Original error: unknown error: Device emulator-5554 is not online

Im getting above error when at the middle of the test steps. Im with Appium, C# on android.

Can any one give me a properer solution for above error?

  • Can you check - whether its connected properly using cmd "adb devices" and let me know – NarendraC Nov 30 '16 at 10:12
  • Yeah its every time connected properly and screen never get turns off – ChathuD Nov 30 '16 at 12:42
  • can paste me the response? – NarendraC Nov 30 '16 at 13:44
  • info: Chromedriver: Killing any old chromedrivers, running: FOR /F "usebackq tokens=5" %a in (netstat -nao ^| findstr /R /C:"9515 ") do (FOR /F "usebackq" %b in (TASKLIST /FI "PID eq %a" ^| findstr /I chromedriver.exe) do (IF NOT %b=="" TASKKILL /F /PID %a)) > info: Chromedriver: No old chromedrivers seemed to exist > info: Chromedriver: Spawning chromedriver with: E:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe --url-base=wd/hub --port=9515 – ChathuD Dec 2 '16 at 3:48
  • > info: Chromedriver: [STDOUT] Starting ChromeDriver 2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a) on port 9515 > Only local connections are allowed. > info: JSONWP Proxy: Proxying [GET /status] to [GET] with no body > info: JSONWP Proxy: Got response with status 200: "{\"sessionId\":\"\",\"status\":0,\"value\":{\"build\":{\"version\":\"alpha\"},\"os\":{\"arch\":\"x86_64\",\"name\":\"Windows NT\",\"version\":\"6.3\"}}}" – ChathuD Dec 2 '16 at 3:50

You should use the correct device name - "emulator-5554" is probably not your correct device name.

To fix this:

  1. Run: adb devices
  2. It should show: emulator-5554 device ( device means it is online)
  3. To get device name use: adb -s emulator-5554 shell getprop ro.product.name
  4. This will give you a device name use it in set capability i.e. cap.SetCapability("deviceName", "VS Emulator 5.5-inch Marshmallow (6.0.0) XXXHDPI Phone");
  • I also forgot mention that use the UUID in capability as well Code: var cap = new DesiredCapabilities(); cap.SetCapability("deviceName", "donatello"); cap.SetCapability("platformVersionVersion", "6.0.0"); cap.SetCapability("uuid", ""); cap.SetCapability("fullReset", "True"); cap.SetCapability(MobileCapabilityType.App, "Browser"); cap.SetCapability("platformName", "VS Emulator 5.5-inch Marshmallow (6.0.0) XXXHDPI Phone"); – BehranG BinA Jan 4 '17 at 3:34

info: Chromedriver: No old chromedrivers seemed to exist...

Could it be driver related?

When you install the Appium server, a chrome driver is being downloaded as well and that is the one being used by default. Now it could be that the one Appium is trying to use is to old compared to the one installed on the device (or the other way around).

There are couple of workarounds that might fix your issue.

  1. Install the latest Chrome app on the phone (see apkmirror website)
  2. Install Appium with the latest Chromedriver npm install appium --chromedriver_version="2.16"
  3. Run Appium with a Chromedriver you've downloaded manually appium --chromedriver-executable /path/to/my/chromedriver


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.