Using meraki-node-sdk generates a fatal error when calling DevicesController.claimNetworkDevices.
This appears to be because the API is specified in meraki/openapi as returning an HTTP 200 for this request, even though the actual API behaviour returns no response payload (should be HTTP 204 in that case).
I reported this issue back in September 2019, however it appears it has gone ignored:
https://github.com/meraki/meraki-node-sdk/issues/1
We have worked around this issue in the meantime by calling the API without the assistance of the SDK, can you please advise whether we should expect a fix?
Additionally, if you are not monitoring GitHub issues for your repositories - can you please disable them to avoid confusion?
Solved! Go to solution.
Actually, this was already fixed in the September release! Just update your SDK to the latest version,
(diff)
Thanks for bringing this up. I've responded to the issue within GitHub.
- We are looking at fixing this from both an API and SDK perspective.
Cheers for the reply, good to know it's on the radar 🙂
Actually, this was already fixed in the September release! Just update your SDK to the latest version,
(diff)
... egg on my face - thanks for the heads up, I'll make sure we've rolled forwards to the latest version!