You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I configured the Travis-CI browserstack addon according to this document, karma-browserstack-launcher will always receive an "access denied" when running in travis-ci.
The reason is that travis-ci will always add a suffix "-travis" to your browserstack username and also set this new username to the process.env.BROWSERSTACK_USERNAME.
The workaround is to set process.env.BROWSERSTACK_USERNAME to your original username at the top of karma.conf.js but I hope this issue can be fixed in karma-browserstack-launcher or at least mentioned in the README/FAQ.
If I configured the Travis-CI browserstack addon according to this document, karma-browserstack-launcher will always receive an "access denied" when running in travis-ci.
The reason is that travis-ci will always add a suffix "-travis" to your browserstack username and also set this new username to the process.env.BROWSERSTACK_USERNAME.
https://github.com/travis-ci/travis-build/blob/10491086722c72e8bd73672c76d9e1947c70b3c1/lib/travis/build/addons/browserstack.rb#L182

Then this modified browserstack username is used by karma-browserstack-launcher, according to the code below.
karma-browserstack-launcher/index.js
Line 42 in 22ccf91
The workaround is to set process.env.BROWSERSTACK_USERNAME to your original username at the top of karma.conf.js but I hope this issue can be fixed in karma-browserstack-launcher or at least mentioned in the README/FAQ.