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.

Sign up for GitHub

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

Jump to bottom

QoS 2 persistence provider should use sequence number instead of message id #37

Closed

nayato opened this issue Mar 11, 2016 · 1 comment

Assignees

Labels

bug

Member

nayato commented Mar 11, 2016

MessageId is meant for users in IoT Hub and it may be null + there is no uniqueness guarantee for it.

nayato added the bug label

nayato self-assigned this

Member Author

nayato commented Mar 12, 2016

fixed by #38

nayato closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment