Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment from VSC 1.10 to Azure functions failed: 'func' is not recognized #3556

Closed
PauloNLopes opened this issue Feb 5, 2023 · 6 comments · Fixed by #3558
Closed

Deployment from VSC 1.10 to Azure functions failed: 'func' is not recognized #3556

PauloNLopes opened this issue Feb 5, 2023 · 6 comments · Fixed by #3558

Comments

@PauloNLopes
Copy link

Deployment from VSCode v1.09 to Azure functions was working well until VSCode was updated automatically to v1.10 a few days ago (Feb 2, 2023). Now deployment yields an error:

Error: Command "func --version" failed with exit code "1": 'func' is not recognized as an internal or external command, operable program or batch file.

I reverted back to VSCode v1.09 and deployment is working again. Could you pls advise if and when this is fixed?

Many thanks

@PauloNLopes
Copy link
Author

Sorry, in my message above I was referring to the v1.9.0 and v1.10.0 Azure Functions extension for VSCode. I'm using VSCode v 1.74.3. Repeating below with this correction:

Deployment from VSCode to Azure functions using Azure Functions extension v1.9.0 was working well until the VSCode Azure Functions extension was updated automatically to v1.10.0 a few days ago (Feb 2, 2023). Now deployment yields an error:

Error: Command "func --version" failed with exit code "1": 'func' is not recognized as an internal or external command, operable program or batch file.

I reverted back to VSCode Azure Functions extension v1.9.0 and deployment is working again. Could you pls advise if and when this is fixed?

Many thanks

@BarendDS
Copy link

BarendDS commented Feb 6, 2023

I have the same issue

@mbbcardoso01
Copy link

Same issue here

@nturinski
Copy link
Member

Thanks for bringing this to our attention. We've identified the cause of the bug and are currently working on a fix for it. 🙂

@nturinski
Copy link
Member

This should be fixed! Please update to v1.10.1 and try it out. If you're still running into issues, let us know!

@m-scipione
Copy link

Worked for me, thanks for jumping on it!

@microsoft microsoft locked and limited conversation to collaborators Mar 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants