Open dimkin-eu opened 4 years ago
Hey @dimkin-eu
In case you need to run both the desktop app as well as use Webdriver IO for an automate test, you can use the local identifier option in your WebdriverIO configuration.
This will allow both the local connections to be run simultaneously (Desktop app for local + local binary for WebdriverIO)
You need to add the below
bs_local_args = { 'key': '<browserstack-accesskey>', 'localIdentifier': 'randomstring' }
Refer: https://github.com/browserstack/browserstack-local-nodejs#local-identifier
In your capabilities, within bstack:options
, you need to add the same identifier using you defined in bs_local_args
.
Your bstack:options
block should look like:
"bstack:options": {
"os": "Windows",
"osVersion": "10",
"resolution": "1920x1080",
"networkLogs": "true",
"video": "false",
"localIdentifier": "randomstring",
"seleniumVersion": "3.141.59"
}
This will prevent the error from showing up
@shawnlobo96 a little bit cumbersome, and looks like another workaround :) And which id BrowserStackLocal uses? to not set the same ( you know, human random is pseudorandom :) )
@dimkin-eu this is indeed another workaround. Browserstack local does not set a local identifier by default. Ideally, when you require multiple binaries to be run with the same access_key
, you would use a local identifier as this allows for multiple binaries to be spawned with the same credentials. This identifier can be any random characters or numbers.
Also, the local identifier you use is specific to your account.
Let's say you are using local identifier abc
with your access_key, that would not affect my execution even if I specify the local identifier as abc
since our accounts are different.
TLDR: you need to have the same localIdentifier
in your capabilities as that used to start up the binary. You can think of it as a kind of mapping that maps the running test session with the binary instance.
You can write at 'support@browserstack.com' in case you still have any further questions or feedback :)
Environment (please complete the following information):
Config of WebdriverIO common things, apart this
Describe the bug BrowserStack dropped old app, and the new app creates problems for running
To Reproduce
Expected behavior test runs
Log
For a workaround is not enough to uninstall the app or just kill running processes - you need to kill both ( app is pretty smart :) )