"Create workflow..." fails with "Cannot read properties of undefined (reading 'fsPath')" error

brad302 commented 7 months ago

Describe the Bug with repro steps

Go to Azure extension
Select "Azure LogicApps" button from the workspace accordion/section
"Create Workflow..."

The following error occurs ...

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "Call_a_local_function_in_this_logic_app": {
                "type": "InvokeFunction",
                "inputs": {
                    "functionName": "MyFunctionRenamed",
                    "parameters": {
                        "zipCode": 85396,
                        "temperatureScale": "Celsius"
                    }
                },
                "runAfter": {}
            },
            "Response": {
                "type": "Response",
                "kind": "http",
                "inputs": {
                    "statusCode": 200,
                    "body": "@body('Call_a_local_function_in_this_logic_app')"
                },
                "runAfter": {
                    "Call_a_local_function_in_this_logic_app": [
                        "Succeeded"
                    ]
                }
            }
        },
        "triggers": {
            "When_a_HTTP_request_is_received": {
                "type": "Request",
                "kind": "Http"
            }
        },
        "contentVersion": "1.0.0.0",
        "outputs": {}
    },
    "kind": "Stateful"
}

Screenshots or Videos

As already shown in the steps to recreate. Unfortunately, I have no more information than that.

I do also have this issue (which I thought may be related) ...

and after finding an associated issue (https://github.com/microsoft/vscode-azurefunctions/issues/3773) that was resolved, unfortunately, my workspace only has a single .csproj file and the context of that issue isn't exactly the same.

Browser

Chrome

Additional context

No response

AB#25875619

CharlesWarwick commented 7 months ago

I am seeing this behaviour and it started immediately after updating the VS Code LAS extension to 2.81.5

immediately after the reload in the image, I could not create a workflow and got this error.
When I reverted to v2.72.2 I could create workflows again

brad302 commented 7 months ago

@CharlesWarwick thanks for the heads up ...! Very helpful.

ccastrotrejo commented 7 months ago

HI all, thanks for raising this issue. I will take a look at this and come up with a fix

ccastrotrejo commented 7 months ago

Ok I have created this PR https://github.com/Azure/LogicAppsUX/pull/3779 to fix this bug. We will include the fix in the next release of the extension

Azure / LogicAppsUX