1

I'm using the Appium GUI to try to connect with the cloud servers at BitBar. I have entered the capabilities, including my API key and app id, and the connection starts successfully. However, once the app loading screen comes up, the test stops due to the following error:

Command timeout, no command received in last 0 seconds. Did you call webdriver quit()?

I don't know what I'm doing wrong, can someone point me in the right direction?

Symon Hambrey
  • 35
  • 4

1 Answers1

0

You just have to increase newCommandTimeout or remove that capability. It seems you set it to 0.

If you use Appium Desktop, it's here, according to appium changelog Bitbar handles 0 value improperly. It's going to be fixed soon.

maszter
  • 3,680
  • 6
  • 37
  • 53
  • Do I put that command in the desired capabilities? I haven't set any timeouts so far. This is my desired capability list: { "platformName": "Android", "platformVersion": "8.0", "bitbar_apiKey": "", "bitbar_device": "Google Pixel XL", "bitbar_app": "", "bitbar_target": "android", "deviceName": "Android Phone", "automationName": "Appium" } – Symon Hambrey Nov 19 '19 at 09:06
  • I don't know, the default value is 60 when you don't set it. However, in logs I can see that 0 came from you. Maybe it's specific to the client/driver you use? – maszter Nov 19 '19 at 13:18
  • Maybe, it's certainly not something I set myself, but it's working now – Symon Hambrey Nov 19 '19 at 14:14