Wim Selles

Hi @jayandran-Sampath This is the logic I now have in the appium-boilerplate https://github.com/webdriverio/appium-boilerplate/blob/ea3ae3a622c3d68945ac30989f23191addeed58a/tests/helpers/Utils.ts#L12 Not sure if we also want to implement that

@christian-bromann I've been thinking about this one, and also about your remark > I believe if users can use the url command to open a resource and it works for...

I think I would then use the name `deepLink` instead of `open` because `deepLink` is more common in the mobile world. Otherwise we would introduce a new command which could...

Cool! Will put it on my agenda to work on it before the end of the year

@christian-bromann No, it doesn't. I'm checking internally what the issue is. This works  but this doesn't 

nope, that fails in WDIO because it expects a rule object

@christian-bromann When I change this in the `saucelabs.json` file ```json "parameters": [{ "name": "rule", "type": "object", "description": "A rule describing the request interception.", "required": true }] ``` to (don't mind...

Shall I create a PR for this? It's a pretty easy fix, but also needs a website release By the way, I like this ```js await browser.interceptRequest({ url: 'https://www.saucedemo.com/v1/index.html', redirect:...

ok, will first create a PR for it

Hmm, @christian-bromann It might not be as easy, see https://docs.saucelabs.com/insights/debug/#intercept-network-requests There are multiple options: - redirect - error - response How should I handle that in the protocol?