Open bmeijwaard opened 4 years ago
Also opened an issue here at Microsoft.Azure.SignalR: https://github.com/Azure/azure-signalr/issues/776
We have the exact same problem with our .Net Core 3.1 v3 functions that attempt to send SignalR messages: Sometimes it works correctly but after a while MissingMethodException
begin to appear. Restarting the function appears to sometimes fix the problem for a while, but it inevitably returns.
According to our logs the problem started around February 5, which seems to close to the time when we upgrade our functions from from V2 to V3.
After performing a memory dump we noticed our function loaded D:\Program Files (x86)\SiteExtensions\Functions\3.0.13107\32bit\System.IdentityModel.Tokens.Jwt.dll
version 5.5.0.60624, thus not the System.IdentityModel.Tokens.Jwt.dll
we ship with our function code.
Since Microsoft.Azure.WebJobs.Extensions.SignalRService
version 1.0.2 has a transitive dependency on System.IdentityModel.Tokens.Jwt
version 5.2.1 and we therefore ship this older version we thought we had found the problem and attempted to fix it by adding a direct dependency on Microsoft.Azure.SignalR.Management
version 1.4.0 which, which ensures we also ship transitive dependencies that depend on version 5.5.0 of System.IdentityModel.Tokens.Jwt
.
After testing we however soon noticed this did not solve the problem.
Function app info in case someone from the Azure function team can take a look at logs from their side:
Fixed problem was fixed by https://github.com/Azure/azure-signalr/issues/776#issuecomment-591459921
Receiving mentioned error as of today, yesterday it was working fine. Currently using Azure SignalR standard price tier set on 'Default' service mode.
The expetion is raised when using this method, calling signalRMessage.AddAsync:
Exception:
Package.json: