New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session * was terminated due to BROWSER_TIMEOUT #7567
Comments
These are your client logs. We need the appium server logs. |
Server logs attached. Thanks! |
same issue using Android devices running parallel on Grid. seem look like Grid displays node is ready for next testcase and receives request to create new driver but on Appium server side still old session is not cleared |
Can someone help me on this? |
Is this issue been looked into? @jlipps , any updates on this ? We are seeing test failures every day and every time we run our suite it is going red. |
That log is not from the latest version of Appium. Please try with Appium 1.6.3 instead. |
@jlipps , yes, we are in the process of upgrading to the new appium version. But is there a solution for the older version(v1.5.3)? |
Just to add - upgrading to v1.6.3. is not a solution because that version is not working with real iOS devices. Unable to codesign the IntegrationApp. |
@MEZISH if you're having problems with real devices, upgrade to 1.6.4 and file your own issue if you're noticing a problem. Closing this for now. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The problem
Running test suite on various IPHONE simulators using Grid is throwing BROWSER_TIMEOUT error. We are seeing this issue from the last 3 or 4 weeks.
Environment
Details
Running test suite on various IPHONE simulators using Grid is throwing BROWSER_TIMEOUT error. We are seeing this issue from the last 3 or 4 weeks.
Link to Appium logs
I cannot access https://gist.github.com. So, I am pasting logs here itself.
The text was updated successfully, but these errors were encountered: