Open mcollier opened 2 years ago
Hi @mcollier , @apawast , any updates on this? I also face this issue and at the moment can't debug. Is there any known workaround? (Maybe downgrading an extension/core-tools)?
I have the same issue, reinstall of core-tools does not help.
In my case, %UserProfile%.azure-functions-core-tools\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows contained 2 versions - 1.8.9 and 2.21.0. Not sure where did the version 2.21.0 came from. I followed advice mentioned in https://github.com/Azure/logicapps/issues/348 to delete the offending version. Debugging started working after that.
When attempting to debug a Logic App (Standard) app in VS Code, I seem to be running into the same issue as stated at azure/logicapps#518.
This seems to be a problem only when debugging in VS Code. If I run
func host start
, the Logic App starts successfully. Runningfunc host start --verbose
, shows the runtime does find the extension bundle, but at a different location, /home/vscode/data/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows.I do have a folder at ~/.azure-functions-core-tools/Functions/ExtensionBundles, but it doesn't contain Microsoft.Azure.Functions.ExtensionBundle.Workflows, only Microsoft.Azure.Functions.ExtensionBundle.
It seems that the Logic Apps VSCode extension is asking
func.exe
for the path to the bundle, and the path returned is different than the actual location of the bundle.