Open Hammad1954 opened 1 month ago
@Hammad1954 but due to an exception, the session is not allocated to the driver
If the session is not allocated then the sessionId will be null. In your screenshot I see a sessionId present, we only allocate a session once we receive the id from appium driver.
Also from client side you need to handle the driver.quit so that plugin knows that it needs to take care of clearing all the required stuff.
thanks for the clarification @saikrishna321
but I have noticed many time i receive exception The HTTP request to the remote WebDriver server for URL http://192.168.0.116:4723/wd/hub/session timed out after 60 seconds.
from client driver but still session get started on device and on build page.
@Hammad1954 Please share full logs when this error happens.
I will send the log once it occurred. but this option could be use full when sometime the automation script crashes and you dont have the access to driver.
Hello @saikrishna321
Please find the logs for above issue
https://gist.github.com/Hammad1954/f3ed47d06f970a4fcdb4855e8590dcb6
@Hammad1954 Sorry, everything looks fine in the logs. I don't see any timeout happening in the logs.
@saikrishna321 I think I have to increase the wait time of appium session to start which in 60 sec by default to 120 sec.
[FEATURE ENHANCMENT REQUEST]
We need an option to terminate a live build session from the Appium Device Farm browser UI. At times, a session is initiated from the Appium driver, but due to an exception, the session is not allocated to the driver. In such cases, we are left with no option but to restart the server.