Disconnection issues with Mobile Devices

[dtothefp]

Update

BrowserStack support recommended the following configs. Seems to fix my issue, feel free to close if this seems unrelated to this plugin:

captureTimeout: 3e5,
browserNoActivityTimeout: 3e5,
browserDisconnectTimeout: 3e5,
browserDisconnectTolerance: 3

Original Issue

This may not be an issue with this plugin, and I've submitted a BrowserStack support request, but I thought I would cover my bases and submit the issue here as well.

Recently, we started having disconnection on iPhone tests typically after a specific number of tests "50 out of 201". I'm not sure if there is a setting in karma-browserstack-launcher that could help avoid disconnection?

From this video it looks as if the tests are completing successfully but still getting a "disconnection" which makes me think there is some sort of problem of communication between this plugin and BrowserStack http://cl.ly/1v0x1b2u1A3l

//****BS CONFIG**** 
{ username: 'xxxxx',
  accessKey: 'xxx',
  localIdentifier: 'bleepbloop',
  project: 'v1.0.7 [local:integration]',
  build: 'donate-frontend',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  tunnelIdentifier: 'bleepbloop' }
//****BS RUN CONFIG**** 
{ key: 'xxx',
  localIdentifier: 'bleepbloop',
  jarFile: undefined,
  hosts: [ { name: 'localhost', port: 9876, sslFlag: 0 } ],
  proxyHost: null,
  proxyPort: null,
  proxyUser: null,
  proxyPass: null }

//***SETTINGS PASSED TO WORKER ****
 { os: 'OS X',
  os_version: 'El Capitan',
  device: undefined,
  browser: 'firefox',
  tunnelIdentifier: 'bleepbloop',
  browser_version: '43.0',
  url: 'http://localhost:9876/?id=65511367',
  'browserstack.tunnel': true,
  timeout: 300,
  project: 'v1.0.7 [local:integration]',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  build: 'donate-frontend' }
***SETTINGS**** { os: 'Windows',
  os_version: '7',
  device: undefined,
  browser: 'ie',
  tunnelIdentifier: 'bleepbloop',
  browser_version: '11.0',
  url: 'http://localhost:9876/?id=61845585',
  'browserstack.tunnel': true,
  timeout: 300,
  project: 'v1.0.7 [local:integration]',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  build: 'donate-frontend' }
***SETTINGS**** { os: 'WINDOWS',
  os_version: '8.1',
  device: undefined,
  browser: 'chrome',
  tunnelIdentifier: 'bleepbloop',
  browser_version: '46.0',
  url: 'http://localhost:9876/?id=90547240',
  'browserstack.tunnel': true,
  timeout: 300,
  project: 'v1.0.7 [local:integration]',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  build: 'donate-frontend' }
***SETTINGS**** { os: 'OS X',
  os_version: 'El Capitan',
  device: undefined,
  browser: 'safari',
  tunnelIdentifier: 'bleepbloop',
  browser_version: '9.0',
  url: 'http://localhost:9876/?id=82673358',
  'browserstack.tunnel': true,
  timeout: 300,
  project: 'v1.0.7 [local:integration]',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  build: 'donate-frontend' }
***SETTINGS**** { os: 'ios',
  os_version: '8.3',
  device: 'iPhone 6 Plus',
  browser: undefined,
  tunnelIdentifier: 'bleepbloop',
  browser_version: 'latest',
  url: 'http://localhost:9876/?id=3218706',
  'browserstack.tunnel': true,
  timeout: 300,
  project: 'v1.0.7 [local:integration]',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  build: 'donate-frontend' }
***SETTINGS**** { os: 'android',
  os_version: '4.4',
  device: 'Samsung Galaxy S5',
  browser: undefined,
  tunnelIdentifier: 'bleepbloop',
  browser_version: 'latest',
  url: 'http://localhost:9876/?id=44703457',
  'browserstack.tunnel': true,
  timeout: 300,
  project: 'v1.0.7 [local:integration]',
  name: 'firefox, ie, chrome, safari, iPhone 6 Plus, Samsung Galaxy S5',
  build: 'donate-frontend' }

Typically the test disconnects after running 50 out of 201 tests

[shirish87]

@dtothefp those config values should fix this issue. Mobile simulators need higher timeout values for them to work reliably.

[forresto]

Worth adding to the README.

[bengummer]

I've noticed that mobile browsers (specifically Safari on iOS) will timeout if the actual Karma test area (when fixtures/elements are inserted) is pushed outside of the device viewport by lots of Karma " is executing..." rows. This typically happens if you are running more than 1 or 2 browsers against a Browserstack mobile device.

A short term workaround for this is to run mobile browsers first, so that there is less chance that the fixture area will be off-screen.