-
Notifications
You must be signed in to change notification settings - Fork 442
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
Could not load file or assembly 'System.IdentityModel.Tokens.Jwt, Version=5.6.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' after upgrading Azure Function's nuget packages to 3.0.4 or 3.0.5 #5756
Comments
We upgraded Microsoft.NET.Sdk.Functions to version 3.0.5 and the issue still persists. Unfortunately it has become a roadblock unless we do not upgrade. /cc @paulbatum |
I'm also getting this issue but with Microsoft.IdentityModel.Tokens 5.6.0 nuget package. |
@Arash-Sabet @kuromukira we'll take a closer look at this. In the meantime, you can also add the following property to your project (which will allow you to upgrade): <_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput> |
Just came here to confirm the issue. |
same error and solution worked but i'm using v1.0.34 |
Got into same problem... and worked out that it works with: |
Hi @TKC-GitHub , thank you for the information. |
yes and it didn't work the only way to make it working was to downgrade one of them as per my previous comment |
We have had an Azure Function V3 that has a reference to another C# project in a VS 2019 solution. There are some extension methods in the other C# project using System.IdentityModel.Tokens.Jwt Version=5.6.0.0 assembly to perform token validation. The Azure Function has been working fine by using those extension methods to validate token. The following code snippet shows the nuget packages:
We upgraded the nuget packages in the azure function according to the following list and started receiving the exception reflected the title of this ticket. What's the solution or workaround to solve this problem?
For now, we had to downgrade the packages again to be able to move forward.
/cc @jeffhollan @anthonychu
The text was updated successfully, but these errors were encountered: