Describe the bug
When running an app created from the latest templates (definitely meadow-startkit, possibly others), there is an ESP32 error about configuration logged to the output.
The ESP32 has had an error (InvalidConfigurationFile).
To Reproduce
Steps to reproduce the behavior:
Install WildernessLabs.Meadow.Template v1.12.2
Create a new project (e.g., dotnet new meadow-startkit)
Run the app on a Meadow device
Log level: Information
Device is configured to use WiFi for the network interface
The ESP32 has had an error (InvalidConfigurationFile).
All cloud features are disabled.
Expected behavior
No errors about default, provided template config.
Workaround
It appears this is a result of the meadow.config.yaml file's contents, specifically the Coprocessor: and Network: lines. If these are empty but the parent object isn't commented out, it will cause that error. Commenting them out makes the error go away.
Describe the bug When running an app created from the latest templates (definitely
meadow-startkit
, possibly others), there is an ESP32 error about configuration logged to the output.To Reproduce Steps to reproduce the behavior:
dotnet new meadow-startkit
)Expected behavior No errors about default, provided template config.
Workaround It appears this is a result of the meadow.config.yaml file's contents, specifically the
Coprocessor:
andNetwork:
lines. If these are empty but the parent object isn't commented out, it will cause that error. Commenting them out makes the error go away.