Every JavaScript V2 HTTP-triggered function gives 404 in Azure - runs fine locally

[ChristianWeyer]

I have a created a very simple and plain HTTP-triggered JavaScript function in VS Code - all with the latest runtimes and tools.
You can find it here: /~https://github.com/ChristianWeyer/azure-functions-js-http-repro

Running it locally, everything is fine, e.g. http://localhost:7071/api/ping
However, after deploying it (via VS Code) to Azure, I get a 404. E.g. https://cwplayground.azurewebsites.net/api/ping

BTW: this happens with all the HTTP-triggered JavaScript functions I have tried to build and deploy.

[mhoeger]

@ChristianWeyer - I know you commented on #3584, but did changing or adding the App Setting FUNCTIONS_WORKER_RUNTIME => node work as a workaround to unblock you?

[ChristianWeyer]

Indeed, that helped. Sorry for not having seen this :-/

Is there any ETA for a fix?
Thanks!

[mhoeger]

@ChristianWeyer - glad that helped! Could you tell us how you deployed your function? And do you have FUNCTIONS_WORKER_RUNTIME defined in local.settings.json?

[ChristianWeyer]

I deployed it via the Azure tools in VS Code.

Yes, the setting is there:

[mhoeger]

@ChristianWeyer - I've haven't been able to repro your issue when creating a new function app and deploying through VS Code (see image).

I think that the function app you're deploying to may have been created with runtime stack of "dotnet", which gave it the FUNCTIONS_WORKER_RUNTIME app setting of "dotnet". By default, local.settings.json environment variables are not copied over, as App Settings are often secrets and credentials.

We do want to improve this experience though, because FUNCTIONS_WORKER_RUNTIME does not change in local vs. prod. The tracking issue for that fix is here: #3120

[ChristianWeyer]

So, I guess we can close it for now.