azure-functions-core-tools: Null reference exception when debugging from VS
Hi Guys,
I have installed Microsoft Visual Studio Enterprise 16.8.0 Preview 2.1 yesterday and now can’t run Azure Functions locally.
System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=func
StackTrace:
at Azure.Functions.Cli.Utilities.LogLevelExists(IConfigurationRoot hostJsonConfig, String category) in D:\a\1\s\src\Azure.Functions.Cli\Common\Utilities.cs:line 208
Azure Functions Core Tools (3.0.2852 Commit hash: d1c2c8e7dc10a94a399246dda94049a7dbf0383d) Function Runtime Version: 3.0.14287.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 25 (6 by maintainers)
Temporary, copied all from AzureFunctionsTools/Releases/ 3.10.0 folder/files into the AzureFunctionsTools/Releases/ 3.11.0.
@jaliyaudagedara
Core Tools version 3.0.14287.0 was just released and VS updates to the latest version automatically.
Fix is merged with the linked PR. New version of core tools is released.
Please note that there is a try … catch here
https://github.com/Azure/azure-functions-core-tools/blob/674ea7a0dd605e6c61349839129596841c1a8f30/src/Azure.Functions.Cli/Common/Utilities.cs#L206-L213
Until we release a fix for the null ref, when debugging - please select do not break on this exception.
I’m having the exact same issue, just started today. I just ran a function app locally that was running fine a few days ago. Saw that it briefly flashed “downloading core tools” when it started up, so obviously it updated them. Now my app won’t run - I get the same error:
at Azure.Functions.Cli.Utilities.LogLevelExists(IConfigurationRoot hostJsonConfig, String category) in D:\a\1\s\src\Azure.Functions.Cli\Common\Utilities.cs:line 208
This is with:
Azure Functions Core Tools (2.7.2855 Commit hash: 674ea7a0dd605e6c61349839129596841c1a8f30) Function Runtime Version: 2.0.14248.0
Here is my host.json: