You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As outlined in eclipse-threadx/getting-started#337, the customer had a hard to diagnosing the returned error from his call to the json writer as it returned a generic error NX_AZURE_IOT_SDK_CORE_ERROR.
Upon investigation, it seems that this function swallows all errors from the embed c-sdk. In this case the user was unable to know that they had exceeded the memory buffer, even though this is reported back to nextduo, until he debugged into the function.
The preference would be to map the underlying c-sdk errors codes to netxduo errors codes and return these to the customers.
The text was updated successfully, but these errors were encountered:
As outlined in eclipse-threadx/getting-started#337, the customer had a hard to diagnosing the returned error from his call to the json writer as it returned a generic error NX_AZURE_IOT_SDK_CORE_ERROR.
Upon investigation, it seems that this function swallows all errors from the embed c-sdk. In this case the user was unable to know that they had exceeded the memory buffer, even though this is reported back to nextduo, until he debugged into the function.
The preference would be to map the underlying c-sdk errors codes to netxduo errors codes and return these to the customers.
The text was updated successfully, but these errors were encountered: