From 00247a763737232e0e5548f5ebe99fde82d6f465 Mon Sep 17 00:00:00 2001 From: Archit Aggarwal Date: Fri, 9 Oct 2020 10:55:12 -0700 Subject: [PATCH] Remove extraneous call to MQTT_ProcessLoop (#333) --- .../MQTT_Mutual_Auth/DemoTasks/MutualAuthMQTTExample.c | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Mutual_Auth/DemoTasks/MutualAuthMQTTExample.c b/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Mutual_Auth/DemoTasks/MutualAuthMQTTExample.c index 4295920e3..e6c35da69 100644 --- a/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Mutual_Auth/DemoTasks/MutualAuthMQTTExample.c +++ b/FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Mutual_Auth/DemoTasks/MutualAuthMQTTExample.c @@ -415,16 +415,6 @@ static void prvMQTTDemoTask( void * pvParameters ) * strategy implemented in retryUtils. */ prvMQTTSubscribeWithBackoffRetries( &xMQTTContext ); - /* Process incoming packet from the broker. After sending the subscribe, the - * client may receive a publish before it receives a subscribe ack. Therefore, - * call generic incoming packet processing function. Since this demo is - * subscribing to the topic to which no one is publishing, probability of - * receiving Publish message before subscribe ack is zero; but application - * must be ready to receive any packet. This demo uses the generic packet - * processing function everywhere to highlight this fact. */ - xMQTTStatus = MQTT_ProcessLoop( &xMQTTContext, mqttexamplePROCESS_LOOP_TIMEOUT_MS ); - configASSERT( xMQTTStatus == MQTTSuccess ); - /****************** Publish and Keep Alive Loop. **********************/ /* Publish messages with QoS1, send and process Keep alive messages. */ for( ulPublishCount = 0; ulPublishCount < ulMaxPublishCount; ulPublishCount++ )