Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not find path to extension bundle

See original GitHub issue

VSCode Dump

Does this occur consistently? Yes Repro steps:

Open Application folder with Visual Studio Code
Press F5

Action: azureLogicAppsStandard.getDebugSymbolDll Error type: Error Error Message: Could not find path to extension bundle.

Version: 1.0.34 OS: win32 OS Release: 10.0.19044 Product: Visual Studio Code Product Version: 1.72.0 Language: en

Call Stack

extension.bundle.js:2:6296338extension.bundle.js:2:6296338
extension.bundle.js:2:6295377extension.bundle.js:2:6295377
P extension.bundle.js:2:6295063
getExtensionBundleFolder extension.bundle.js:2:6295969
extension.bundle.js:2:6296593extension.bundle.js:2:6296593
extension.bundle.js:2:6295377extension.bundle.js:2:6295377
P extension.bundle.js:2:6295063
getDebugSymbolDll extension.bundle.js:2:6295878
extension.bundle.js:2:4136498extension.bundle.js:2:4136498
extension.bundle.js:2:4113256extension.bundle.js:2:4113256
extension.bundle.js:2:4112074extension.bundle.js:2:4112074
P extension.bundle.js:2:4111760
callWithTelemetryAndErrorHandling extension.bundle.js:2:4113163
extension.bundle.js:2:4136216extension.bundle.js:2:4136216
extension.bundle.js:2:4135752extension.bundle.js:2:4135752
P extension.bundle.js:2:4135438
extension.bundle.js:2:4136027extension.bundle.js:2:4136027
n._executeContributedCommand extensionHostProcess.js:90:111324
n.$executeContributedCommand extensionHostProcess.js:90:112028
i._doInvokeHandler extensionHostProcess.js:100:13680
i._invokeHandler extensionHostProcess.js:100:13362
i._receiveRequest extensionHostProcess.js:100:12132
i._receiveOneMessage extensionHostProcess.js:100:11033
extensionHostProcess.js:100:8941extensionHostProcess.js:100:8941
p.invoke extensionHostProcess.js:61:145
v.deliver extensionHostProcess.js:61:2266
b.fire extensionHostProcess.js:61:1844
c.fire extensionHostProcess.js:69:19049
extensionHostProcess.js:116:17106extensionHostProcess.js:116:17106
p.invoke extensionHostProcess.js:61:145
v.deliver extensionHostProcess.js:61:2266
b.fire extensionHostProcess.js:61:1844
c.fire extensionHostProcess.js:69:19049
s._receiveMessage extensionHostProcess.js:69:23861
extensionHostProcess.js:69:21304extensionHostProcess.js:69:21304
p.invoke extensionHostProcess.js:61:145
v.deliver extensionHostProcess.js:61:2266
b.fire extensionHostProcess.js:61:1844
b.acceptChunk extensionHostProcess.js:69:15880
extensionHostProcess.js:69:15010extensionHostProcess.js:69:15010
Socket.d extensionHostProcess.js:69:27128

Steps to Reproduce the Bug or Issue

Open Azure Logic App Standard Application with Visual Studio Code (previously Logic App Standard App work fine)
Press F5
Error shown: Could not find path to extension bundle. Source: Azure Logic App Standard Extension

What I saw is that Azure Logic App Standard Extension is updated 6 hours ago, I try to revert to previous version but same issue happened. Application can not start locally, and designer also can not open for the workflows.

AB#15943509

Side effect: Right click on workflow in Azure Logic App Standard and choose Open in Designer. Designer will never open, and popup error message with next output: 8:42:02 AM: Running command: “func GetExtensionBundlePath”… 8:42:04 AM: Could not find path to extension bundle 8:42:04 AM: {“status”:1,“signal”:null,“output”:[null,“”,“Unable to locate extension bundle.\r\n”],“pid”:47560,“stdout”:“”,“stderr”:“Unable to locate extension bundle.\r\n”} 8:42:04 AM: Error: Could not find path to extension bundle. 8:46:50 AM: Running command: “func GetExtensionBundlePath”… 8:46:51 AM: Could not find path to extension bundle 8:46:51 AM: {“status”:1,“signal”:null,“output”:[null,“”,“Unable to locate extension bundle.\r\n”],“pid”:119524,“stdout”:“”,“stderr”:“Unable to locate extension bundle.\r\n”} 8:46:51 AM: Error: Could not find path to extension bundle. 9:32:17 AM: Running command: “func GetExtensionBundlePath”… 9:32:17 AM: Could not find path to extension bundle 9:32:17 AM: {“status”:1,“signal”:null,“output”:[null,“”,“Unable to locate extension bundle.\r\n”],“pid”:85008,“stdout”:“”,“stderr”:“Unable to locate extension bundle.\r\n”} 9:32:17 AM: Error: Could not find path to extension bundle. 9:41:14 AM: Running command: “func host start --port 8000”…

Azure Functions Core Tools Core Tools Version: 3.0.4585 Commit hash: N/A (64-bit) Function Runtime Version: 3.7.1.0

[2022-10-21T07:41:16.429Z] Error fetching version information for extension bundle Microsoft.Azure.Functions.ExtensionBundle.Workflows [2022-10-21T07:41:16.433Z] Unable to find or download extension bundle [2022-10-21T07:41:16.934Z] No job functions found. Try making your job classes and methods public. If you’re using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you’ve called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.). For detailed output, run func with --verbose flag. [2022-10-21T07:41:21.904Z] Host lock lease acquired by instance ID ‘0000000000000000000000001668EE14’. 9:43:43 AM: Running command: “func host start --port 8000”… Port 8000 is unavailable. Close the process using that port, or specify another port using --port [-p]. 9:48:06 AM: Error: 404 - undefined

This could be also useful info: when I start: func host start --verbose: Capture