Getting "Azure SignalR Service is not connected yet, please try again later." when upgrading Microsoft.AspNetCore.Http.Connections.Client to 6.0.0.0

[chrfin]

Describe the bug

I have a classic ASP.NET MVC project targeting .NET 4.7.1 using SignalR and Microsoft.Azure.SignalR.AspNet.
If I upgrade Microsoft.AspNetCore.Http.Connections.Client from 5.0.12.0 to 6.0.0.0 I get the following error with status code 500 when the client calls /negotiate:

Azure SignalR Service is not connected yet, please try again later.

To Reproduce

Create a classic ASP.NET MVC project and use the packages mentioned above.

Exceptions (if any)

I do not get any exceptions, just the mentioned 500 during negotiation.

Further technical details

I'm using 1.13.0 of the Microsoft.Azure.SignalR.AspNet package and when I enable logging like described HERE I get the following log entry:

Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Failed to connect to '(Primary)https://MY-SERVICE.service.signalr.net', will retry after the back off period. Error detail: Method 'get_Features' in type 'Microsoft.Azure.SignalR.WebSocketConnectionContext' from assembly 'Microsoft.Azure.SignalR.Common, Version=1.13.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation.. Method 'get_Features' in type 'Microsoft.Azure.SignalR.WebSocketConnectionContext' from assembly 'Microsoft.Azure.SignalR.Common, Version=1.13.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation.. Id: a23d8224-6c1d-4ef7-bbe0-5f150a299275

I guess there was a property changed with v6 of the Microsoft.AspNetCore.Http.* classes.
If you can't reproduce with the given information, please tell me and I will create a repro-repo 🤓.

[vicancy]

Looks causing by dotnet/aspnetcore#32307 that in 6.0 ConnectionContext this IFeatureCollection Features is considered to be in assembly Microsoft.Extension.Features

However WebSocketConnectionContext implements Features in assembly Microsoft.AspNetCore.Http.Features

As a result, it believes get_features is not implemented.

Hi David @davidfowl, do you have insights on how to handle such breaking changes?

[vicancy]

There is an on-going effort to fix this issue as tracked in dotnet/aspnetcore#38699

[chrfin]

Update, as I just hit the same error again trying to update some dependencies:

The following three packages are required to be kept below v6.*:
* Microsoft.AspNetCore.Connections.Abstractions
* Microsoft.AspNetCore.Http.Connections.Common
* Microsoft.AspNetCore.Http.Connections.Client

The newest v5.* as to date is 5.0.17 and does still work.

[chrfin]

@vicancy / @davidfowl Any update on this? v5.0.17 is now deprecated and v8.0.2 still does not work...

[jaydgus]

@vicancy / @davidfowl Any update on this? v5.0.17 is now deprecated and v8.0.2 still does not work...

Did you get the latest assemblies to work?

[ionelr]

@vicancy / @davidfowl Any update on this? v5.0.17 is now deprecated and v8.0.2 still does not work...

Did you get the latest assemblies to work?

I just tried with those 3 packages versions 8.0.2 and 8.0.5 (latest), they DO NOT work
5.0.17 (deprecated) works
issue still present

[jaydgus]

The following three packages are required to be kept below v6.*:

• Microsoft.AspNetCore.Connections.Abstractions
• Microsoft.AspNetCore.Http.Connections.Common
• Microsoft.AspNetCore.Http.Connections.Client

The newest v5.* as to date is 5.0.17 and does still work.

This is still an issue. I updated our nugets and it broke the client-side signalR negotiation. I had to roll these 3 back to 5.0.17 to get it to work.

[jaydgus]

Did this get resolved or just closed? Did this package's support end?

…

On Thu, Sep 26, 2024, 8:30 PM Liangying.Wei ***@***.***> wrote: Closed #1503 <#1503> as completed via #2049 <#2049>. — Reply to this email directly, view it on GitHub <#1503 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZAKQOM256OXHMPFNJPMWTZYSYKPAVCNFSM5JKZ3XBKU5DIOJSWCZC7NNSXTWQAEJEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW4OZRGQ2DENBTGAYDMNRV> . You are receiving this because you commented.Message ID: ***@***.***>

[vicancy]

The code fix is in. We will release a stable version of the package after validation cycle. Please allow me to update the package status once its released.

[vicancy]

https://www.myget.org/feed/azure-signalr-dev/package/nuget/Microsoft.Azure.SignalR.AspNet contains the preview version containing the fix, we will release a stable version after validation workflow.

[vicancy]

1.28.0 https://www.nuget.org/packages/Microsoft.Azure.SignalR.AspNet containing the fix is released.

[jaydgus]

Awesome, thanks for the update!

…

On Sun, Sep 29, 2024, 7:17 PM Liangying.Wei ***@***.***> wrote: 1.28.0 https://www.nuget.org/packages/Microsoft.Azure.SignalR.AspNet containing the fix is released. — Reply to this email directly, view it on GitHub <#1503 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZAKQOUCK6F7BZ2I4EJNUTZZCKALAVCNFSM5JKZ3XBKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZYGE3DSMBRGQ2Q> . You are receiving this because you commented.Message ID: ***@***.***>