TypeError: Cannot set property 'isHandled' of undefined

[vegard_bakke]

After upgrading to Qlik Sense February 2018 SR 1, we have started to get the console error:

   TypeError: Cannot set property 'isHandled' of undefined

in our mashup application.

Anyone with the same experience, or hints for sollutions?

Cheers

[vegard_bakke]

Looks like I get an error i the websocket.  Anyone knows how to read this?

Request:

1. delta:true
2. handle:1
3. id:4
4. jsonrpc:"2.0"
5. method:"CreateSessionObject"
6. params:
   1. 0:
      1. qInfo:
         1. qId:"MUjcKMLP"
         2. qType:"CurrentSelections"
      2. qSelectionObjectDef:
         1. qStateName:"$"

Reply:

1. error:
   1. code:15
   2. message:"Request aborted"
   3. parameter:"Failure"
2. id:4
3. jsonrpc:"2.0"

I have no idea what goes wrong here...

[vegard_bakke]

Looks like a CreateSessionObject("CurrentSelections") is conflicting with a ClearAll(), that's being fired at the same time. It only happens 1 out of 10 times, and was not a problem in v3.1, but is a problem now under the Feb 2018 SR1 release.

[ErikWetterberg]

Hi,

The 'Request aborted' error is a normal situation, something Qlik should handle. If everything seems to work you do not need to worry (even if the error looks like a bug). To avoid too many 'Request aborted' you could (and should) make any initial clearAll, applyBookmark etc before creating sessionObject, calling getObject etc.

Something like this:

app.clearAll().then(function(){
 app.createSessionObject(...);
});

Erik Wetterberg

[vegard_bakke]

Thank you. I was not aware of that.

It looks like we have solved our problem.

Initially, we had an issue when following the spec in v3.1, regarding that clearAll() returned in the client before it was completely completed on the server.  We got a working workaround for 3.1, but this might be wrong now with Feb 2018.

Apparently, all our web programmer did, was going from the callback approach to the ```async``` approach. (I didn't do it, so unfortunately I don't have any code examples for anyone else in the same situation.)

We have not had a single instance of the previous "'isHandled' of undefined" error since.

Appreciate your input, as always!