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
After creating an MqttServer instance, I add an event handler for ClientAcknowledgedPublishPacketAsync:
_mqttServer.ClientAcknowledgedPublishPacketAsync += OnClientAcknowledgedPublishPacketAsync;
Every time a message is published to a client and acknowledged by the client, the event handler function OnClientAcknowledgedPublishPacketAsync() is called twice.
Which component is your bug related to?
Server
To Reproduce
Using version 4.1.2.350 of MQTTnet.
See the description for steps to reproduce.
Expected behavior
When a client receives and acknowledges a message, the ClientAcknowledgedPublishPacketAsync event handler is only called once.
Screenshots
n/a
Additional context / logging
n/a
The text was updated successfully, but these errors were encountered:
Ok then I assume this is the issue. I will fix this so that the event only gets called after the PUBCOMP message is received because only this message clearly marks the successful end of the transfer process.
Describe the bug
After creating an MqttServer instance, I add an event handler for ClientAcknowledgedPublishPacketAsync:
_mqttServer.ClientAcknowledgedPublishPacketAsync += OnClientAcknowledgedPublishPacketAsync;
Every time a message is published to a client and acknowledged by the client, the event handler function OnClientAcknowledgedPublishPacketAsync() is called twice.
Which component is your bug related to?
To Reproduce
Using version 4.1.2.350 of MQTTnet.
See the description for steps to reproduce.
Expected behavior
When a client receives and acknowledges a message, the ClientAcknowledgedPublishPacketAsync event handler is only called once.
Screenshots
n/a
Additional context / logging
n/a
The text was updated successfully, but these errors were encountered: