Replying to @coderbyheart
It's because of these error messages I'm not really excited about this upgrade:
2 replies
Replying to @coderbyheart
Aaand of course I found a bug already:
https://github.com/aws/aws-iot-device-sdk-js-v2/issues/176
Cramming a C library through Node.js is such a PITA.
Replying to @coderbyheart
I absolutely need to catch connection exceptions during end-to-end tests because
we use JITP and the device will get disconnected on the first connect. During
the test this is expected and needs to be gracefully handled in the test run.