-
Notifications
You must be signed in to change notification settings - Fork 432
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
Http Trigger Fails to Start With net8.0-windows + Azure.Identity #10084
Labels
Comments
@andrew-rheingans Just curious to know why you need to use |
I use the function to generate some images and the package that generates those images targets net8.0-windows. |
microsoft-github-policy-service
bot
added
Needs: Attention 👋
and removed
Needs: Author Feedback
labels
May 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check for a solution in the Azure portal
For issues in production, please check for a solution to common issues in the Azure portal before opening a bug. In the Azure portal, navigate to your function app, select
Diagnose and solve problems
from the left, and view relevant dashboards before opening your issue.When targeting net8.0-windows and the Azure.Identity package is installed (though not directly referenced), my http trigger fails to load. If I change the target to net8.0, it works. OR, if I remove the Azure.Identity package, it works. But with both of those it fails. Also, when I run it locally, it works. I wasn't sure if I should post this here or on the azure sdk repo, but since it works locally but not when deployed, I figured I would start here. I created a basic repo to reproduce the issue - see below for details.
Investigative information
These are from the test function I created to reproduce the problem:
Repro steps
Expected behavior
Http trigger loads.
Actual behavior
Http trigger fails to load.
Known workarounds
Avoid using Azure.Identity. Change to net8.0 (not an option for me but does fix it)
Related information
Here is an example repo that reproduces the issue: https://github.com/Anchora-Solutions/FunctionStartFailure
And that is deployed to https://function-start-failure.azurewebsites.net
Also, here are the logs I've found for host startup:
The text was updated successfully, but these errors were encountered: