operations fail if arguments go out of scope

[marcusb]

The MQTTAgent_Publish() method requires that the pPublishInfo argument (carrying the topic name) remains in scope after the call returns. This is not documented in the API doc, which only says:

The context passed to the callback through pCmdContext member of pCommandInfo parameter MUST remain in scope at least until the callback has been executed by the agent task.

I am allocating the parameters to the Publish call on the stack, and do not want to wait for an ack, just send a fire-and-forget request. I can do this by setting the callback pointer to NULL. But that still doesn't work, because the library retains the pPublishInfo pointer. But that memory is deallocated when my method returns, leading to undefined behavior.

Perhaps the library should make a copy of the supplied MQTTPublishInfo_t instead.

[jasonpcarroll]

Hi @marcusb,
I will take a deeper look at this. Thank you for bringing it to attention!
Best,
Jason Carroll

[rawalexe]

Hello @marcusb,
Increasing the priority of the mqtt task can help out with solving this issue. We will also update the doc to reflect this requirement. Please let us know if you have more questions

[AniruddhaKanhere]

Hello @marcusb,

Firstly, apologies for the delay on our part.

Secondly, I see your point. Thank you for reporting this issue.
We will update the documentation. But the behavior of the library cannot be easily changed.

For your application to work, as @rawalexe mentioned above, can you raise the priority of the coreMQTT-Agent? That will cause the agent to wake up as soon as your task adds any data to the agent queue and process it. This will cause your task to be preempted and sleep while the Agent uses the passed arguments to send publish packet. When it is done, your task will wake up and it will be okay to free the memory used by the arguments.

Let us know if this works.

Thanks,
Aniruddha