The function type name '{0}' is invalid

[GitMarJansen]

From Azure DevOps I deployed my Azure function. When navigating to the Azure Portal and opening the function, I received a message (in a pink box like the one mentioned in #541). After some binging, I found #541 and discovered that redeploying the function could solve my problem and indeed it did.
The solution for #541 should not be redeploying, but a fix in the deployment process. For that reason #541 should not be closed!
Please solve the cause of this issue, because validating if the function is correctly started after each deploy is painful.
Thanks,
Hilmar

[ColbyTresness]

@ahmedelnably can you take a look?

[ahmedelnably]

@GitMarJansen do you mind sharing with us which Azure DevOps template you are using to deploy your function app? there is a new release template that is optimized for Azure Function

[GitMarJansen]

This is the one we are using: version 4 of Azure App Service Deploy

In the step before, we configure the function-app using an ARM template.

[ahmedelnably]

Do you mind trying out the new Azure Functions deploy task

[GitMarJansen]

Thanks, works like a charm! Better solution than mentioned in #541

[GitMarJansen]

I am running into this issue again when I deploy a new azure function app.

There is no feedback of what is wrong, just showing me ({FunctionApp}/{FunctionName}) and The function type name is invalid. The name mentioned is the full namespace + classname as defined in code. None of the functions in this app are working anymore...

[GitMarJansen]

Hmmm. somehow the following appeared in my config: FUNCTIONS_EXTENSION_VERSION = ~1. It is not part of my code, neither of the deploy task... It magically appears after deploying a new function app. This appears to be killing the azure function. Took me 3 hours to discover this. #889

[tomkerkhove]

We had the same issue where the Azure DevOps task assigned ~1, after changing it to ~2 it was fixed.

[rgomns]

I also have the error "The function type name {0} is invalid" but can't use the solution to use the devops pipeline because the previous dev used 2 different accounts for devops and azure (personal and work account). Whenever i try to create a azure function pipeline i recieve the message "You don’t appear to have an active Azure subscription.".

Please help because the function was working before i made a change in the if statement and now it doesn't work and it is a really critical process for our company.

[chrisparkeronline]

I ran across this today with deploying a .net core 3 function using azure pipelines. Changing the FUNCTIONS_EXTENSION_VERSION to ~3 fixed the issue.

[blueelvis]

This is happening for me as well where using PowerShell to publish a Function is setting it to v1 and then redeploying fixes it. I checked and during the initial creation, the FUNCTIONS_EXTENSION_VERSION is set v1 sometimes and then once redeployed, it gets set properly to v3.