Closed pcbing closed 5 years ago
I have no idea where this comes from, but what I can tell is that MQTT5 currently isn't fully supported in the server project.
I'm not sure, but can you maybe try:
Console.WriteLine($"+ Payload = {Encoding.UTF8.GetString(e.ApplicationMessage.Payload)}");
instead of:
var hex = String.Concat(Array.ConvertAll(payload, x => x.ToString("X2")));
Console.WriteLine($"payload received:{hex}");
from the example under https://github.com/chkr1011/MQTTnet/wiki/Client#consuming-messages?
After replacing MQTTnet.AspNetCore.SpanBasedMqttPacketWriter with MQTTnet.Formatter.MqttPacketWriter, it works.Maybe something wrong in class MQTTnet.AspNetCore.SpanBasedMqttPacketWriter
@JanEggers Do you know what's wrong? I assume some wrong buffer offsets, lengths etc.?
@chkr1011 I can reproduce the error in a test, will work on a fix now
@chkr1011 fixed pr is on the way, not sureif we need more testcoverage on v5, @pcbing thx for reporting it
Perfekt 👍 I will release this with the upcoming release of 3.0.7.
And yes we need more tests for 5.0.0 😄
@pcbing Please test 3.0.7-rc2.
It works,thanks
It works,thanks
@JanEggers I am interested what the error was. Can you explain a little bit?
I increased the 'bytes written' counter twice when copiing a subwriter. that added N times 0 where N is the size of the subwriter.
Describe the bug
After a message is published, the message received through the mqtt server changes
Which project is your bug related to?
To Reproduce
Steps to reproduce the behavior:
Screenshots
payload published:313233343536 payload received:000000000000000000000000000000000000000000000000000000000000000000000000000000000000313233343536
Code example