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
"No job functions found" after updating to 2.0.12050.0 #928
Comments
Thank you for creating this issue. |
@jmsalvo -- I was able to create a brand-new Function app in VS and successfully start it up, so let's try to figure out what's different between our two setups. When you look in your output folder (typically I'm trying to see if maybe the new bits aren't getting dropped into your folder somehow... |
Yes, I see 2.0.0-beta4 listed as the Product version for Microsoft.Azure.WebJobs.Extensions.EventGrid.dll |
Can you share the console output when you hit F5? (Make sure there's no secrets that get logged...) |
Not sure if this is note-worthy, but if I remove "version": "2.0" from my hosts.json file I don't see any errors when I run the function in VisualStudio. I thought this setting is required, or would be set automatically when the functions is started...but I don't see this happening. |
Thanks for calling it out (you never know what the difference could be). That's expected -- if you don't have the "version" and have an otherwise-empty host.json, we'll just continue along since you wouldn't hit any breaking changes. |
Another thing to try. Create a new Function app and add the same references you have above (but you can skip the ExtensionsMetadataGenerator). If you right-click and add a new function and pick EventGrid (just leave it as the default), then run -- does it work? |
Ok, I will give that a try. I can also post the output from the console. |
Another thing to look at -- the "extensions.json" file in your output directory. What's it have in it? |
extensions.json is empty |
I presume that file should be populated with the appropriate extensions, but for some reason is not |
Ahh, that's likely it. Try deleting it and rebuilding? Or even delete the whole bin folder and rebuild... |
I tried deleting bin folder and rebuild, but I still see an empty extensions.json file. It does seem that the extensions.json file not being populated is the culprit, just unsure how to get it updated with the correct extensions. |
Can you remove your nuget reference to "Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator" Version="1.0.0"? |
yes, I'll remove that reference. |
Also can you delete the obj folder, it will force refresh the targets that are responsible for generating the extensions.json |
Removing that nuget reference for the ExtensionsMetadataGenerator resolved the issue of the extensions.json file being empty. I'm now seeing extensions listed in that file. Going to try running the function |
I am no longer seeing the binding extension errors when I run my function, thank you very much for your assistance. |
I had the same issue with CosmosDB trigger. |
I had the same issue on one of our build agents (not locally) with QueueTrigger. |
Alright... so I found this issue and among the breaking changes that happened earlier... I had to install the func extensions install -p Microsoft.Azure.WebJobs.Extensions.Http -v 3.0.0-beta8 Just an FYI. |
Unfortunately, I am not having any luck with this!! I tried removing and adding.....the extensions.json in the netstandard2.0 folder is empty:
I have a VS2017 15.8.2 with several function apps in the same solution. The solution compile...I tried cleaning up, rebuilding, removing In the first function app, I have the following NuGet packages:
In the second function app, I have the following NuGet packages:
Both are generating empty I am also at loss as to where the extensions.json file should be. I have 2 other function apps in the same solution that have no extensions. On one, i see an |
I'm experiencing the same issue as @eilefh.
When I have the reference locally I have warnings when building You can try using this repo https://github.com/klesouza/azure-functions2-sample, if you remove the reference and build the docker image again, no |
I am having a similar issue here. Referenced in #953. Locally everything builds and runs but deployment will not run and I have observed an empty I tried referencing sdk version 1.0.21 |
Was able to workaround my binding issue by copying over my local extensions.json file to the remote host via cloud explorer. |
I have the same issue in my environment. Azure DevOps build pipeline with .NET Core build task doesn't produce proper extensions.json file. Same code compiled by VS produces proper extensions.json file. BTW, no explicit reference to the Microsoft.Azure.Webjobs.Script.ExtensionsMetadataGenerator in the projects. Apparently, dotnet build is different from VS build. During VS build "MSBuildRuntimeType = Full", in the dotnet build "MSBuildRuntimeType = Core". This variable controls the behavior of the task that generates extensions.json file. See .nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.0.1\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets file for details. In VS, the build process uses .nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.0.1\tools*net46*\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.dll IMHO, the problem in the .NET Core version of the Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.dll As a workaround, I've switched the ADO build pipeline to perform Visual Studio build instead of .NET Core. Now my CI process generates generates correct extensions.json file, consistent with the what developers workstation produces. PS. I my case proper extensions.json has below content:
|
@brettsam Do you guys have any news on this one? |
@brettsam any update here? |
I'm pretty sure we've solved all of the original issues (moving ExtensionsMetadataGenerator forward). Since this is a really generic error, it can happen for a number of reasons. Can anyone still seeing this please let us know your symptoms, specifically:
Note that there was recently a new ExtensionsMetadataGenerator release that fixed some issues with targeting .NET Core 2.1+. If you're having issues, give that a try by directly adding the nuget reference to the newest release: https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator/1.0.2 |
Specifically, I'm seeing an empty extensions.json file next to the host.json file, not in the bin. I'm using a clean project from template v2 with BlobTrigger with updated references.
If I add the workaround provided by @TomBonnerAtTFL Azure/azure-functions-host#4059 then I get the correct output. Edit: even with the workaround there seems to be some sort of race condition. |
I'm getting metadata generation failure on my Mac. This is a gist containing the full error message https://gist.github.com/rogeralsing/a9b1acd0fd650f4d35cb8667c7d4e5a7 The final bit is:
I've tried countless of times to recreate my functions using vs code from scratch, but I hit this issue 100% of the times. |
I have no such file generated, generation fails before it can create it
No |
@rogeralsing -- can you try updating your project to use 1.0.26 of Microsoft.NET.Sdk.Functions? https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions/1.0.26? Does the issue still happen? |
@brettsam yep, same issue there. It seems to be SDK related because netcoreapp 2.0 builds fine and generates correct metadata. while 2.1 and 2.2 fails on metadata error. I've done complete reinstalls of dotnet core on my machine. and also tried them one by one. still same issue. |
Would you be able to throw your .csproj file into a gist? That may help us track down the issue... |
Thanks @rogeralsing. I've split this off to a separate issue: Azure/azure-functions-host#4181. We'll continue the investigation over there. |
I'm hitting the same issue, I've opened an issue here with all my investigations so far: I have no idea how to continue to investigate from here |
If you debug/run from Visual Studio (F5), somehow, even with latest Microsoft.NET.Sdk.Functions (v1.0.28), its not able to detect AzureFunctions defined in the project. I root caused the issue to Project properties > Debug > Working Directory is not set somehow by default. Set it to the actual directory where binaries are found and your AzureFunctions becomes available for debug. PS, this would add launchSettings.json /profiles/{projectName}/workingDirectory=/objd/amd64/ |
I'm breaking out an issue from our announcements page into it's own topic for more back-and-forth. Original discussion started here: Azure/app-service-announcements-discussions#64 (comment)
From @jmsalvo
The text was updated successfully, but these errors were encountered: