The server floods with an error and leaves the phone busy forever

[Comeodore]

Device farm 8.4.6 https://gist.github.com/Comeodore/546c7db91e7d948aa54ab060e757042e

Session didnt drop, no session in url/device-farm/api/devices on device with udid emulator-5554, and in web this devices is "busy" but didnt have session id below In logs of node this 'busy' device is also present

Reproduced on normal test runs quite often, because of this, the test can simply freeze dead when the session with the driver is running

UPD. after 10-15 minutes device still busy

@saikrishna321

[saikrishna321]

@Comeodore Emulator 5554 has a session created and its busy, i don't see any delete session call for the device to be unblocked.

NewCommandTimeout is 600seconds and that is the reason why the device remains busy thinking that appium might send a command.

Logic: if newCommandTimeout exceeds appium by default will send a delete session call and device-farm will unblocked the device.

Let me check if appium sends the delete call when newCommandTimeout is expired.

[Comeodore]

i don't see any delete session call for the device to be unblocked

@saikrishna321 I specially add request for force delete session when driver is stopped, but i tryied get session id from device-farm and this is empty, like on my screenshot, can we do smth with that?

[saikrishna321]

i don't see any delete session call for the device to be unblocked

@saikrishna321 I specially add request for force delete session when driver is stopped, but i tryied get session id from device-farm and this is empty, like on my screenshot, can we do smth with that?

Sorry I quite don't get your ask.

[Comeodore]

Sorry I quite don't get your ask.

@saikrishna321 Since sometimes there are problems with completing a session in the appium, to be on the safe side, I always send a request to appium server that the session is completed via requests (request.delete to appium server with session id), but I pull the session id from device-farm, which like, as we see in the screenshot - losted somewhere

My question is, can we do something about the fact that the device is locked and there is no session ID?

[Comeodore]

@saikrishna321 I will try to reproduce this with full logs from hub and node and give it to you, because my tests 100% send driver.quit to appium server

[saikrishna321]

@Comeodore Is this happening when session failed to created??

[Comeodore]

Is this happening when session failed to created??

@saikrishna321 yep

[saikrishna321]

Please try with latest RC and see if this happens

[Comeodore]

Please try with latest RC and see if this happens

Ok, i will try

[saikrishna321]

Fixed.