Create a new Logic App project fails in VS Code

[four-colours-suffice]

Does this occur consistently? Yes Repro steps:

1. Click the button to create a new Logic App project

Action: azureLogicAppsV2.createNewProject Error type: Error Error Message: Failed to get latest templates: certificate signature failure

Version: 0.0.13 OS: win32 OS Release: 10.0.19042 Product: Visual Studio Code Product Version: 1.56.2 Language: en

Call Stack

``` CentralTemplateProvider. extension.bundle.js:164:445752 fulfilled extension.bundle.js:164:442307 ```

[vikash-anand]

@four-colours-suffice We have updated our extension. Can you install the latest extension and try again? The latest extension should fix this issue.

[ShreeDivyaMV]

@four-colours-suffice , did you get a chance to verify with the latest extension? Please let us know if any issues.

[four-colours-suffice]

Hi, This is still not working. I have created a logic app using the Logic Apps (Standard) extension, I can't run it locally. I am following this guide: Create workflows with single-tenant Azure Logic Apps (Standard) in Visual Studio Code - Azure Logic Apps | Microsoft Docs https://docs.microsoft.com/en-us/azure/logic-apps/create-single-tenant-workflows-visual-studio-code Because I am running in a corporate environment I cannot use NGROK, so I have used a schedule instead of an HTTP trigger, so my Logic App should just send me an email according to a schedule, but when I click the run icon to run the app nothing seem to happen. If I click Run |Start debugging the Select a process to attach to opens, but I have no clue as to which process I should attach to (why do I need to attach to a process?)

Guides and videos make using Visual Studio Code seem simple and easy, but I don't find this to be the case!

Regards,

Matt

On Tue, 3 Aug 2021, 07:52 ShreeDivyaMV, @.***> wrote:

@four-colours-suffice https://github.com/four-colours-suffice , did you get a chance to verify with the latest extension? Please let us know if any issues.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/logicapps/issues/289#issuecomment-891584051, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHTH26PD5K2LCR4CSJ73EMTT26G3NANCNFSM45JKDUIA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

[ShreeDivyaMV]

@four-colours-suffice, when you click on debug, the debug symbols are supposed to be loaded for logic app. Could you verify the 'tasks.json' file of your VS code project has the below tasks added? It would by default be added when a logic app project is created. In case it is modified, it might cause these issues.

You can copy the below content into tasks.json and verify if it works.

{ "version": "2.0.0", "tasks": [ { "label": "generateDebugSymbols", "command": "dotnet", "args": [ "${input:getDebugSymbolDll}" ], "type": "process", "problemMatcher": "$msCompile" }, { "type": "func", "command": "host start", "problemMatcher": "$func-watch", "isBackground": true } ], "inputs": [ { "id": "getDebugSymbolDll", "type": "command", "command": "azureLogicAppsStandard.getDebugSymbolDll" } ] }

[four-colours-suffice]

I copied your json into tasks.json (I think mine was the same anyway) but the behaviour is still the same

On Wed, Aug 11, 2021 at 8:34 AM ShreeDivyaMV @.***> wrote:

@four-colours-suffice https://github.com/four-colours-suffice, when you click on debug, the debug symbols are supposed to be loaded for logic app. Could you verify the 'tasks.json' file of your VS code project has the below tasks added? It would by default be added when a logic app project is created. In case it is modified, it might cause these issues.

You can copy the below content into tasks.json and verify if it works.

{ "version": "2.0.0", "tasks": [ { "label": "generateDebugSymbols", "command": "dotnet", "args": [ "${input:getDebugSymbolDll}" ], "type": "process", "problemMatcher": "$msCompile" }, { "type": "func", "command": "host start", "problemMatcher": "$func-watch", "isBackground": true } ], "inputs": [ { "id": "getDebugSymbolDll", "type": "command", "command": "azureLogicAppsStandard.getDebugSymbolDll" } ] }

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Azure/logicapps/issues/289#issuecomment-896573964, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHTH26JN3K54SHWR5C5ZL53T4IRZ7ANCNFSM45JKDUIA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

-- ho ho ho

[ShreeDivyaMV]

@four-colours-suffice , thanks for trying this out. I hope the Launch.json file also has the logic app process attached, as below. If not, please update. If possible, would you be able to share the project folder?

{ "version": "0.2.0", "configurations": [ { "name": "Attach to .NET Functions", "type": "coreclr", "request": "attach", "processId": "${command:azureLogicAppsStandard.pickProcess}" } ] }

[ShreeDivyaMV]

@four-colours-suffice , Did you get a chance to verify the above? If the issue isn't occurring now or you would require more time to get back, we can temporary close this thread and you can reopen it anytime.