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.
Failed to Deploy Function App Code - Extension V1.6.1
See original GitHub issueOS: Windows 11 Enterprise Build Version: 10.0.22000 Function Core Tools: v3/4 Regression: Previous release
Repro Steps:
- Open a previously working PowerShell Azure Function app code
- Attempt to re-deploy code using the Azure Function extension - “Deploy to Function App”
Expect: The previous function app ZIP code to be re/deployed
Actual: Fail to redeploy function app code
OUTPUT LOG:
10:37:38 func-m365: Starting deployment...
10:37:39 func-m365: Creating zip package...
10:37:39 func-m365: Zip package size: 54.9 kB
10:42:17: Error: request to https://func-m365.scm.azurewebsites.net/api/zipdeploy?isAsync=true&author=VS%20Code failed, reason: read ECONNRESET
More Info:
This issue appeared in an environment I have been using for about 12 months and started on the 2022-03-24 which co-incides with V1.6.1 of the extension.
This was the last successful message in the “Deployments” folder from a deployment on the 2022-03-23
2022-03-23T17:52:51.890Z - Updating submodules.
2022-03-23T17:52:52.423Z - Preparing deployment for commit id '17ad008132'.
2022-03-23T17:52:53.942Z - Skipping build. Project type: Run-From-Zip
2022-03-23T17:52:55.168Z - Skipping post build. Project type: Run-From-Zip
2022-03-23T17:52:55.418Z - Triggering recycle (preview mode disabled).
2022-03-23T17:52:55.871Z - Deployment successful.
I get the same error though, when trying to deploy the code to a new function app “+ Create new Function App in Azure...”
Issue Analytics
- State:
- Created a year ago
- Comments:14 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The title mentions the extension version, but it seems like this is related to this issue: https://github.com/microsoft/vscode-azurefunctions/issues/2844 where it’s actually VS Code upgrading to Node V16 that is causing the issue.
We are currently investigating this issue, but for now the workaround is unfortunately to downgrade to any 1.65.x build of VS Code. We’re very sorry for the inconvenience.
Same issue with VSCODE 1.66 and Azure Functions 1.61. After downgrading Azure Functions to 1.6 and VSCODE to 1.65 resolved the issue. To double check, I’ve re-updated Azure Functions extension to version 1.61 (latest). Deployment still works. The only difference between my setup when deployment didn’t work and now that it works is VSCODE version.
My project’s configuration:
Zip package size: 489 kB NodeJS runtime Consumption plan Operating System: Windows Runtime version: 3.5.2.0