Skip to content
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

Browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues. #25

Closed
Automation-Geek opened this issue Mar 22, 2018 · 12 comments

Comments

@Automation-Geek
Copy link

Automation-Geek commented Mar 22, 2018

Hi @andrewtelnov,@maoberlehner , @AlexanderMoskovkin

I am executing my script in IE ,mac and android and getting this error "browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues" most of the time during parallel run in BrowserStack.

My License is quite capable to run n no. instance and it's workk fine for chrome,firefox for windows.

My Application use http-authentication, i used http-auth npm module which eaisly by pass for chrome or firefox but not for mac(safari), ie.

please suggest here , how can i do parallel with all device combimation.

Any help will really appreciate
.

@Automation-Geek
Copy link
Author

any update guys on this ??

@timon-witt
Copy link

timon-witt commented Apr 12, 2018

I have the same problem on Android devices. All browsers and also iPhone works like a charm, no disconnects. But any Android device disconnects every single time right at the start, despite the call being exactly the same as for all other browsers.

I would highly appreciate any update on this issue.

@AndreyBelym
Copy link
Contributor

Hi @guptaakhil, if you use localhost as a testing hostname, try to use 127.0.0.1 or your Network IP, as suggested in this article. Also, try to use ports from this list for testing. You can specify it usng the ports.

@Timywitt, I've reproduced the problem with some Android browsers (Google Pixel, Samsung Galaxy S8) . I'm investigating the problem right now. However, Google Nexus 6 works for me, have you tried to run it?

@timon-witt
Copy link

Google Nexus 6 works for me as well. Even though this is not the solution, thank you very much for finding this out :)

@timon-witt
Copy link

As far as I can tell, these Android devices are the only ones that work:

  • Samsung Galaxy S6, 5.0
  • Google Nexus 6, 6.0
  • Samsung Galaxy Note 4, 6.0

@AndreyBelym
Copy link
Contributor

@Timywitt, I've found the reason of the problem: DevExpress/testcafe#2318 and I'm working on the fix now.

AndreyBelym added a commit to AndreyBelym/testcafe-browser-provider-browserstack that referenced this issue Apr 17, 2018
@Automation-Geek
Copy link
Author

For Samsung devices the node version 6 will not work, it's work fine for Node 4 and v8. I am not sure problem will get resolve because the testcafe browserstack plugin comptable with Node version 6 only.

@Automation-Geek
Copy link
Author

Automation-Geek commented May 22, 2018

@Timywitt @AndreyBelym : this solution is not working for me , Browser becom unresponsive while we running parallel run in ff and chrome in browser Stack. kindly help me to do so.

@hd-esteban
Copy link

hd-esteban commented Jan 18, 2019

I'm facing this issue on Chrome 53.0.2785 / Windows 10.0.0
testcafe version v0.22.0
nodejs version v10.13.0

ERROR The Chrome 53.0.2785 / Windows 10.0.0 (https://automate.browserstack.com/builds/00ee90c744f036dcffece113e5c2ce6bb72c4531/sessions/5a45c0cf6a6b11b8826c3a3e9ca410d2c5db183f) browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues.

I ran the same test case on - Chrome 71.0.3578 / Mac OS X 10.13.6 and everything is working good.

@adaher15
Copy link

adaher15 commented Apr 3, 2019

Hello
I am facing the same issue on Chrome / Mac. The test was running properly until I click on one link that redirect the browser to another page and after a long wait, I got the error:
ERROR The Chrome 73.0.3683 / Mac OS X 10.13.6 browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues.

I can assure that there is no network issue in this case, it's something to do with the way the controller manage the driver.

@AndreyBelym
Copy link
Contributor

@Esteban26, TestCafe doesn't support Chrome versions below Chrome 59,

@adaher15, please try to reproduce the issue on a local machine without BrowserStack, submit a new bug report to the TestCafe repository and provide an example: New Issue: Bug report.

@owen-m1
Copy link

owen-m1 commented Jul 6, 2019

May be same as DevExpress/testcafe#2480

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants