Can't find app with name error while publish the azure function

2
votes

I tried to create an azure function using following link in Ubuntu system(16.04). [azure function][2]

Deployment using arm template and create a local azure function using vs code. Folder contains following files

LocalFunctionProj.csproj, HttpExample.cs, host.json, local.settings.json

azure function is created successfully in portal after deployment.But when i tried to publish the local azure function ,it shows an error Can't find app with name "HttpExample" while using following command

func azure functionapp publish HttpExample

Is anything wrong in my step.

Also i tried this command after 30 mnt when function created in portal

screen shot

2
azureazure-functionsazure-functions-core-tools
what is the name of the function app – Sajeetharan
in locally HttpExample is name.this is the name in the example – avancho marchos
try removing the . after HttpEcample – Sajeetharan
sorry no dots in actual commands. thats not the problem – avancho marchos
do the arm template contains app name and local function name should be the same ? – avancho marchos

2 Answers

1
votes

If you want to publish the local app into azure ,you must create the functional app before in azure portal.Also the name of the azure function is portal should be same as the local azure app.otherwise you can't publish the app.

2
votes

I had a similar issue when I followed a tutorial about Azure Functions Core Tools from Microsoft Learning.

In my case, I had the error Can't find app with name X, because I had a wrong subscription set in my local Azure CLI. The command from below changes subscription for the one that is created with "Microsoft Learning Sandbox". Note that, in your case, the name of the subscription can be different.

az account set --subscription "Concierge Subscription"

If it's not the issue, your question suggests that your function app name should be HttpExample. You need to ensure beforehand that there's a function app with such a name in the subscription you are logged into with Azure CLI.

Moreover, there is a ProvisioningState: Failed in the screenshot, which could also be an issue.