Could not load file or assembly System.IdentityModel.Tokens.Jwt, Version=5.6.0.0

[clinsted]

The error occurs when upgrading Microsoft.NET.Sdk.Functions to version 3.0.4 or 5 from 3.0.3

Full error:
Could not load file or assembly 'System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.":"System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"}

[ErikAndreas]

Got a similar problem. Upgraded from 3.0.2 to .5 and getting runtime exception:
An unhandled host error has occurred.
Could not load file or assembly 'Microsoft.IdentityModel.Protocols, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.

class loaded at runtime (in another project, same solution, if that is of interest) declares (amongst other but prolly related):
using Microsoft.IdentityModel.Protocols;
using Microsoft.IdentityModel.Protocols.OpenIdConnect;
using Microsoft.IdentityModel.Tokens;
using System.IdentityModel.Tokens.Jwt;

adding <FunctionsSkipCleanOutput>true</FunctionsSkipCleanOutput> (child of startup project .csproj PropertyGroup, maybe it should be somewhere else?) has no effect as per suggestion https://twitter.com/codesapien/status/1235999437131898880

[FullStackChef]

@ErikAndreas this worked for me for System.IdentityModel.Tokens.Jwt but note the _ at the begining of functions
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

[ErikAndreas]

Hey @BadTactx it did, thanks! (who'd thought actually doing exactly as stated would work... I though the '_' was for escaping on twitter or something...). For reference:
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>netcoreapp3.1</TargetFramework> <AzureFunctionsVersion>v3</AzureFunctionsVersion> <_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput> </PropertyGroup>
Does seem to work with 3.0.5

[WiredUK]

Just to add my experience too, very frustrating error when publishing to Azure but the _FunctionsSkipCleanOutput property (including the underscore prefix!) worked a treat.

[GuusRaaphorst]

I have the same issue here after upgrading from 3.0.3 to 3.0.5. FYI:

• You can just downgrade to 3.0.3 to fix this.
• Using _FunctionsSkipCleanOutput indeed also works
• Publishing to 2 different (empty) folders changing only _FunctionsSkipCleanOutput shows a big difference in amount of assemblies in the output (function.deps.json and extensions.json are identical):
  • value false: 27 assemblies are copied
  • value true: 92 assemblies are copied
    Missing for false include Microsoft.AspNetCore.* , Microsoft.Extensions.* and System.* assemblies. Hence the 'Could not load file or assembly' message after deploy..

[Dzoukr]

Even if downgrade works (and thanks guys for it!!!), this is quite anoying bug - any update on this?

[brettsam]

For now, using <_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput> is the right approach to getting around this.

I'm going to close this issue and use Azure/azure-functions-host#5894 to track the fix.