Direct DEVICE methods disappear after a while

Having implemented simple direct methods has been working for months, slight unstably with 1.0.6, but no improvements into 1.0.7.21905529.

When trying to active the method, the response is simply (VSCode) “[DirectMethod] Failed to invoke Direct Method: Not found” most of the times. Sometimes it heals itself by some minutes, and retrying might work.

Expected Behavior

The direct methods should always return meaningfully when the device is online.

Current Behavior

The method is not found.

Steps to Reproduce

1. Deploy a direct method in a module written in C#
2. Hack around, wait and try.

Context (Environment)

Device (Host) Operating System

Raspberry Pi 3+ Raspbian GNU/Linux 9.9 (stretch) Release: 9.9

Architecture

arm32

Container Operating System

Linux docker

Runtime Versions

Not sure

iotedged

1.0.7.21905529

Edge Agent

Same

Edge Hub

Same

Docker

3.0.2

Logs

Additional Information

It seems that in the period where the direct methods cannot be found, there is some logs stating some time-out challenges:

2019-05-12 17:52:24.319 +00:00 [INF] - Starting compaction of store deploymentConfig
2019-05-12 18:04:47.928 +00:00 [INF] - Starting periodic operation refresh twin config...
2019-05-12 18:13:47.264 +00:00 [WRN] - Updating reported properties failed with error The operation has timed out. type Microsoft.Azure.Devices.Client.Exceptions.IotHubCommunicationException
2019-05-12 18:18:52.737 +00:00 [WRN] - Updating reported properties failed with error The operation has timed out. type Microsoft.Azure.Devices.Client.Exceptions.IotHubCommunicationException
2019-05-12 18:23:57.867 +00:00 [WRN] - Updating reported properties failed with error The operation has timed out. type Microsoft.Azure.Devices.Client.Exceptions.IotHubCommunicationException
2019-05-12 18:24:03.129 +00:00 [INF] - Updated reported properties
2019-05-12 18:25:36.905 +00:00 [INF] - Obtained Edge agent twin from IoTHub with desired properties version 29 and reported properties version 76.
2019-05-12 18:25:36.909 +00:00 [INF] - Successfully completed periodic operation refresh twin config

[myagley]

The root cause of the connectivity issues are in the C# SDK (which the IoT Edge runtime uses internally). If your module is using the C# SDK, it will also need to be updated to make the end to end flow more stable. The latest C# SDK is version 1.20.1. It is recommended to upgrade to this version.

[github-actions[bot]]

This issue is being marked as stale because it has been open for 30 days with no activity.