Browser: Cannot read property 'messageId' of

[martinzak-zaber]

Hello,

I tried to integrate the library as a replacement for the older aws-iot-sdk. Unfortunately, I am unable to publish messages in a browser. There is an internal callback called, but it looks like the arguments are not passed. The callback then fails when trying to access the packet (argument). Please see the screenshot of the corresponding debugging session.

Callback about the be called. Notice that the object with messageId is actually there but the callback is empty.

The actual code of the callback that tries to access messageId and fails.

Thank you for investigating.

[davepotts]

I'm also experiencing this issue. Its related to the QoS value being set to 0. Higher values do not throw the error

[bretambrose]

Argh, I think I know what this is, but won't be able to get to it for a bit. The QoS 0 is key. We allocate a mqtt packet id for QoS 0 messages in our native mqtt implementation but I'm going to guess that mqtt-js does not and that's what the issue is. I'm not sure what the right resolution here is. I don't think we can make the native and browser behaviors match if the browser doesn't allocate an id. We can certainly stop a crash though, so as a first step we could start with that.

[cyuste]

Also experiencing this error, however, catching and ignoring it "solves" the issue

[bretambrose]

Fix has been released in v1.13.0. v2 SDK release to follow shortly.