Device ConnectionState does not get set when using UWP versions of nuget packages about azure-iot-sdk-csharp

[arturl]

I'll take a look

[olivierbloch]

Hi @v-tbert
You are actually seeing the expected behavior.
First, as mentioned in the documentation, the "connectionState" value should NOT be used in production, but only in debug and development. The reason for this is because the value is not updated for all protocols (it will never be set to true when using HTTP for example), and the meaning of this flag is more "the device was seen at least once in the last x minutes" (X being the TCP idle time for Azure load balancer) rather than an actual indicator of whether or not the device is connected.
We know that this can be confusing and I am about to send out a proposal to the team to have a proper device heartbeat mechanism implemented that would be protocol agnostic.

Now that said, when you use the UWP NuGet package, the device client is created using HTTP by default (as AMQP support for UWP is only arriving now) while when using the package in a .Net app the default protocol used is AMQP. The connectionState is indeed never set when connecting a device running a UWP app.
We should definitively document this and also set the default protocol to the same when possible to ensure the behavior is the same.
I will close this issue as it is NOT a bug in the clients, but a limitation of the service.