The body.id is a faulty one, it should be:a999b57568ab4f44839858e8b879675f. Endpoint responsds with 404 and then karma-sauce-launcher keeps spamming to check the log if any updates did happen… (which is another problem)
It only happens when I am testing real andorid deivces even with latest saucelabs npm package!
Steps to Reproduce the Problem
use karma-sauce-launcher latest
apply package.json:overrides property if necessary to set different versions of webdriver/io
For example in my case I did:
"overrides": {
"webdriver": "^8.32.3",
"webdriverio": "^8.32.3",
"saucelabs": "^4.7.8",
// or use latest, same result tried both
"saucelabs": "^7.5.0",
},
setup for karma sauce launcher such browser capability
Expected Behavior
Expected Android Real device testing to report success in the en.
Actual Behavior
After saucelab succeds with job on real android device, the console stucks in infinite loop.
After debug I see that, the url should be of an available job instead. The saucelab
class SauceLab._get
onthrow new Error(
Failed calling ${propName}: ${err.message}, ${err.response && err.response.body});
catches an failed request error.Details of the requst of
console.log({ method, uri, body })
before that line are for example:The body.id is a faulty one, it should be:
a999b57568ab4f44839858e8b879675f
. Endpoint responsds with 404 and then karma-sauce-launcher keeps spamming to check the log if any updates did happen… (which is another problem)It only happens when I am testing real andorid deivces even with latest
saucelabs
npm package!Steps to Reproduce the Problem
karma-sauce-launcher
latestapply
package.json:overrides
property if necessary to set different versions of webdriver/ioFor example in my case I did:
setup for karma sauce launcher such browser capability
Specifications