-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Managed client cannot send topic alias alone (without topic) #1395
Comments
This was not part of the version you are using. Please try again with the latest version 4 and reopen this ticket if the issue persists. |
I have updated the description. It also exists in v4.1.0.247. I tested it again without any change in behavior. |
Reopened this @chkr1011 |
@SeppPenner Was opening this a mistake? Because I fixed it!? 😁 |
Er sorry, yes... I just read the message and missed the referenced commit... :D |
Describe the bug
I want to use the topic alias feature with the managed MQTT client. I can set the alias but it sends always topic and alias. If I keep the topic empty it throws. But the same advance works with the normal client.
I have seen that client and managed client use different methods for topic validation. I have checked the packet size with Wireshark to see if there is any benefit to the feature.
Is this currently not supported? Have I done something wrong? Is this feature included in a coming version?
Thanks for your work!
Which component is your bug related to?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to be able to publish the second time without the topic. Or the managed client additionally takes care of using topic aliases itself.
Screenshots
As in my example the frist two messages are from the managed client. The second two from an normal client that is working. With the normal client you can see that the feature works but not with the managed client.
Additional context / logging
This is the log of my example app.
Code example
The text was updated successfully, but these errors were encountered: