vscode-azurefunctions icon indicating copy to clipboard operation
vscode-azurefunctions copied to clipboard

Cannot deploy Azure nodejs function after update to v1.15.1

Open olafurfannsker opened this issue 1 year ago • 8 comments

After updating VSCode extension to V 1.15.1, deploying to an existing function using the extension fails with an error message: "Internal error: Expected value to be neither null nor undefined: newSiteName". (newSiteName is nowhere to be found in the project). After downgrading I get the same message so it's a puzzle because it was working before. I'm using VSCode on a MAC with Sonoma.

Publishing through the command line works like a charm.

I tried even to create a new example project and got the same issue.

regards, Olafur

olafurfannsker avatar Jun 25 '24 13:06 olafurfannsker

Hi there, sorry that you're running into problems.

Could you tell me exactly what steps you are doing to deploy? Like, the entry point, what you click after that, etc.

Also, could you try downgrading to v1.14.3 to see if that fixes the error?

nturinski avatar Jun 25 '24 17:06 nturinski

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

AzCode-Bot avatar Jul 11 '24 05:07 AzCode-Bot

I am running to the same issue. Aplication runs fine in local enviroment, but when I go to deploy to azure I get:

"Internal error: Expected value to be neither null nor undefined: newSiteName"

RafaelFN1230 avatar Jul 24 '24 16:07 RafaelFN1230

me too.... the deployment process was working fine a few months ago and nothing changed since

pccsoares avatar Aug 06 '24 09:08 pccsoares

Could you please try running this alpha version of the extension? I think that it may resolve your issue.

  1. Unzip the zip file
  2. In VS Code, press F1 > Install from VSIX
  3. Click the .vsix file that was extracted from the zip file
  4. Reload VS Code

Please let me know if this resolves the deployment issue!

vscode-azurefunctions-1.15.2-alpha.0.zip

nturinski avatar Aug 07 '24 21:08 nturinski

unfortunatelly, the same error still persists. (installed the alpha version and restarted VS Code)

pccsoares avatar Aug 15 '24 15:08 pccsoares

Could you provide some details about your function app? Like runtime, OS, and what app service plan you are using?

If you're able, can you try making a new app and deploying to that?

nturinski avatar Aug 15 '24 17:08 nturinski

Hello @nturinski I am getting the same error. I use net8.0, the worker runtime is dotnet-isolated, functions v4. When I first create the function app and then try to deploy the functions from VS code into this function app I am getting the same error as the others. When I create a new function app while I am deploying the functions in VS code I get NO error, and the deployment works as expected. Next, after deploying to a new function app, I tried to deploy again to an existing function app (from step 1) and this time the deployment worked.

ChristosMonogios avatar Aug 27 '24 07:08 ChristosMonogios

Could anyone having this issue answer how they are deploying their app?

There are a few entry points to start a function deployment:

  1. Right-click a function app node in the tree view, click Deploy to Function App...
  2. Click the function button on the Workspace ribbon and click Deploy to Azure...
  3. Right-click the Local Project node and click Deploy to Azure...
  4. The command palette

nturinski avatar Sep 19 '24 22:09 nturinski

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

AzCode-Bot avatar Oct 04 '24 05:10 AzCode-Bot

Hi I'm facing the same issue after upgrade. Do you know if that will be fixed soon? Do I need to downgrade the version?

RobertoArmas avatar Nov 08 '24 22:11 RobertoArmas

I installed alpha version of the extension. It solve the issue.

RobertoArmas avatar Nov 08 '24 22:11 RobertoArmas