[Bug Report] Version 2.x of iot-device-client, requires version of reported properties to be sent, while 1.x not require that #1776
Labels
Comments
dzakub
changed the title
dzakub
changed the title
dzakub
changed the title
dzakub
added a commit
to dzakub/azure-iot-sdk-java
that referenced
this issue
Feb 23, 2024
…eported properties to be sent, while 1.x not require that Azure#1776
|
PR with a fix: |
timtay-microsoft
added a commit
that referenced
this issue
Mar 11, 2024
…ying the version (#1779) * Fixing issue: Version 2.x of iot-device-client, requires version of reported properties to be sent, while 1.x not require that #1776 * Add integration test for updating reported properties without version Remove some duplicated logic around building a topic string for subscribing to desired properties from MQTT layer --------- Co-authored-by: dzakub <jakubowski.bartosz@gmail.com>
timtay-microsoft
added
the
fix checked in
|
Fixed as of 2.5.0, so I'll close this thread |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Description of the issue
This issue is about compatibility between version 1.x and 2.x.
Behavior in version 1.x:
Sending message to
$iothub/twin/PATCH/properties/reported/#mqtt topic (sendReportedProperties method) without version resulted in no error and client was getting a 200 (OK) response on topic$iothub/twin/res/200/Behavior in version 2.x:
Sending message to
$iothub/twin/PATCH/properties/reported/#mqtt topic (sendReportedProperties method) without version results in error and client was getting a 412 (PRECONDITION_FAILED) response on topic$iothub/twin/res/412/So upgrade to version 2.x causes unnecessary changes for users of client library. Forcing them to manage reported properties version, which can be problematic due to asynchronous and distributed nature of system.
This is a request for reverting behavior to the one present in 1.x version of client.
The text was updated successfully, but these errors were encountered: