There are 2 potential blocking calls when using IoTCredentialProvider… (

#223)

* There are 2 potential blocking calls when using IoTCredentialProvider: Curl & Lws.
The curl call already has logging when the curl_easy_perform fails, however the LWS blocking call did not have any logging on failure.

* Corrected the capitalization, added general error message, but also wanted to keep the specific error message for LWS failure

src/source/Common/Lws/LwsCall.c

@@ -73,6 +73,14 @@ STATUS blockingLwsCall(PRequestInfo pRequestInfo, PCallInfo pCallInfo)
 
 CleanUp:
 
+    if(retStatus == STATUS_IOT_CREATE_LWS_CONTEXT_FAILED)
+    {
+        DLOGW("Unable to create LWS context or connect to Websocket server");
+    }
+    else
+    {
+        CHK_LOG_ERR(retStatus);
+    }
     if (lwsContext != NULL) {
         // Trigger termination
         ATOMIC_STORE_BOOL(&pCallInfo->pRequestInfo->terminating, TRUE);
@@ -259,4 +267,4 @@ INT32 lwsIotCallbackRoutine(struct lws* wsi, enum lws_callback_reasons reason, P
     } else {
         return retValue;
     }
-}
+}