azure-functions-dotnet-worker: Problems with deployed Function App
I’m also dealing with this, unfortunately, and it is critical that I get these functions working ASAP. Any help would be greatly appreciated.
I am not using RunOnStartup, although I did use it during testing prior to release.
I deployed via PowerShell / Azure CLI. I’m seeing:
In Azure Portal, Under Configuration > Function runtime settings, my runtime version is ~3. Under Application Settings:
FUNCTIONS_WORKER_RUNTIME
isdotnet-isolated
FUNCTIONS_EXTENSION_VERSION
is~3
Here’s my .csproj:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net5.0</TargetFramework>
<LangVersion>preview</LangVersion>
<AzureFunctionsVersion>v3</AzureFunctionsVersion>
<OutputType>Exe</OutputType>
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>
<Version>1.1.0</Version>
</PropertyGroup>
<ItemGroup>
<FrameworkReference Include="Microsoft.AspNetCore.App" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Auth0.AuthenticationApi" Version="7.6.0" />
<PackageReference Include="Auth0.ManagementApi" Version="7.6.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.0.12" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Storage" Version="4.0.4" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Timer" Version="4.0.1" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.ServiceBus" Version="4.2.1" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.0.1" OutputItemType="Analyzer" />
<PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.0.0" />
<PackageReference Include="System.Net.NameResolution" Version="4.3.0" />
<PackageReference Include="Microsoft.EntityFrameworkCore" Version="5.0.3" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Relational" Version="5.0.3" />
<PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="5.0.3" />
<PackageReference Include="Scrutor" Version="3.3.0" />
<PackageReference Include="SendGrid" Version="9.22.0" />
<PackageReference Include="Twilio" Version="5.55.0" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\Keystone.Core\Keystone.Core.csproj" />
<ProjectReference Include="..\Keystone.Data\Keystone.Data.csproj" />
<ProjectReference Include="..\Keystone.Logic\Keystone.Logic.csproj" />
</ItemGroup>
<ItemGroup>
<None Update="host.json">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None>
<None Update="local.settings.json">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
<CopyToPublishDirectory>Never</CopyToPublishDirectory>
</None>
</ItemGroup>
</Project>
_Originally posted by @kinetiq in https://github.com/Azure/azure-functions-dotnet-worker/issues/337#issuecomment-808194531_
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (8 by maintainers)
I took a look at this, and I think this is caused by a sync triggers issue that we had fixed some time back. The impact is limited to Windows function apps. Deploying this to a Linux function app should work as expected.
The fixed Azure Functions runtime is mid-deployment right now. The deployment should finish across all regions sometime this week. Once it’s completed, I believe these issues should go away.