After updating to 4.3.0, attempting to get the network response when a filter is applied results in an error "Cannot read property trim of undefined" about wdio-intercept-service HOT 10 CLOSED

@vlohana please upgrade to v4.3.1, released earlier today

from wdio-intercept-service.

That is this line:

cc @jbebe

@chadbellangivelify mind sharing the headers on the request that is causing the issue? You can set a debugger on that line in your test and step in, or add if (parts.length < 2) { console.log('header with only key', line); } to the code in your node_modules, right before the const key = parts[0].trim() line.

from wdio-intercept-service.

If the header row contains a colon, undefined will not occur, even if there is no content after the colon. Given the information there can only be one problem: one of the http headers does not contain a colon. Which is very weird so we you need more context here.

from wdio-intercept-service.

I get the same error too, after updating to 4.3.
I was unable to do any assertions or get methods on the requests.

from wdio-intercept-service.

@sumanthpfs @chadbellangivelify please provide the headers that are causing the issue. You can determine which header is responsible by making a modification in the library's downloaded package (inside node_modules) as identified above

from wdio-intercept-service.

@tehhowch At this time, I'm no longer able to reproduce this issue. Maybe @sumanthpfs Sumanthpfs can provide more details to help

from wdio-intercept-service.

for me it's a request like this causing the problem (added a console log):

{
    __fulfilled: 1669122851503,
    __processed: 1669122851372,
    body: '',
    headers: {},
    method: 'POST',
    requestBody: '[{"event":"map.load","created":"2022-11-22T13:14:11.371Z"}]',
    requestHeaders: { 'content-type': 'text/plain' },
    statusCode: 204,
    url: 'https://events.mapbox.com/events/v2'
}

removed some sensitive info from the url and body.

For the mentioned request, I get the error when parseResponseHeaders is called.

I could investigate next weekend if nobody fixes it by then

from wdio-intercept-service.

im providing a reproductible example here:

1. checkout this branch: dragosMC91/wdio-exclude-pattern-bug-highlight#3
2. (using node 16.18.0) yarn install
3. run yarn test --spec test/specs/suite1/interceptorError.mobile.test.js

Running this test triggers the mentioned error.

from wdio-intercept-service.

Any solution for this issue? I am getting it very often for my application!

from wdio-intercept-service.

closed by #438

from wdio-intercept-service.