You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Timestamp: 2024-04-30T18:39:46.389 (issue is ongoing)
Function App version: 4.33.1.22394
Function App name: function-start-failure
Function name(s) (as appropriate): Function1
Invocation ID: (Function is unable to load)
Region: Central US
Repro steps
Create new "isolated worker" net8.0-windows function app
Add an http trigger
Add Azure.Identity package
Deploy it (it works locally)
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)
@andrew-rheingans Just curious to know why you need to use net8.0-windows as the TargetFramework value for your dotnet-isolated function app. What are you missing when you use net8.0 as the TargetFramework value ?
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: