ESP32 NetworkDeadlock error in app not using network

[patridge]

Describe the bug I have an app that controls some APA102-style LEDs, and that is all it should be doing. While running one test deployment, though, I had two duplicate errors logged that confused me.

The ESP32 has had an error (NetworkDeadlock). The ESP32 has had an error (NetworkDeadlock).

To Reproduce I'm not sure how best to duplicate this error since it has only happened once during a debug deployment.

I currently have nothing uncommented from the meadow.config.yaml under the Network: section (no network interface, NTP, or DNS). And within wifi.config.yaml I have nothing uncommented under the Credentials: section.

Expected behavior When not [intentionally] using networking, I shouldn't see networking errors, let alone deadlocks.

Developer tools (please complete the following information as best as you can):

• OS and version: macOS Sonoma v14.4.1
• IDE and version: VS Code kv1.86.1
• Meadow extension for IDE version: VSCode Tools For Meadow v1.9.6

Meadow (please complete the following information as best as you can):

• Meadow hardware version: Project Lab v3.e (F7Micro, F7CoreComputeV2)
• Meadow OS, Runtime, and Coprocessor version: v1.12.2.0

[duduita]

I removed some unnecessary watchdogs, and left some only in the WiFi code, to allow the device to recover from network deadlocks, since there are still a few issues opened related to that. Then, you should not see any more false positives like that, unless the ESP32 is being used for some reason, even without the network-enabled.

Anyway, although I can't confirm that it fixed the issue, since I don't know how to reproduce it exactly, I'll mark this issue as fixed in the upcoming release, but feel free please to re-open it if necessary.