In some cases, if the browser on the connected virtual android device stops rendering, or if appium doesn’t receive new commands and consequently decides to shutdown UIAutomator, the currently slot of appium will not be released. Therefore, when a new request comes from selenium hub, appium will tell the hub: one was in progress, and hub will fail the request with a message: “A new session could not be created. (Original error: Requested a new session but one was in progress)”.
Did anyone meet this issue, and know how to deal with it? Is there any flag to configure appium to avoid this case?