donetcore 2.2 broke signalr
See original GitHub issueI have the latest aspnetcore 2.2.0 locally, and no longer get OnConnected events in SignalR (authenticated hub). Still using SignalR 1.0.4 on server, client is angular, and doesn’t work with either 1.0.4 or 1.1.0. Same client works with the previous aspnetcore version (2.1.6) with SignalR 1.0.3 and 1.0.4. I get the same problem with both regular SignalR and Azure SignalR.
Client side
"@aspnet/signalr": "^1.1.0",
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:29 (7 by maintainers)
Top Results From Across the Web
Breaking change in AspNetCore 2.2 for SignalR and CORS
This warning actually breaks SignalR – the preflight OPTIONS request fails, and POST /<hubname>/negotiate never happens. Your clients no longer connect to your ......
Read more >Cannot find `SignalR` in `Microsoft.AspNetCore.App` in . ...
All and Microsoft.AspNetCore.App referenced after creating a new ASP.NET Core project (version 2.2). I've even tried Googling and found this ...
Read more >ASP.NET Core 2.2 - SignalR Breaking changes
Problem is that this warning breaks the preflight OPTIONS check of SignalR and the client can no longer connect to the hubs. To...
Read more >SignalR Troubleshooting
Take a look at ASP.NET Core SignalR. This document describes common troubleshooting issues with SignalR. Software versions used in this topic.
Read more >ASP.NET Core 2.2 SignalR Server
SignalR is a technology that allows you to write bi-directional communication between a server and a client. This can lead to some pretty ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This seems to be a workaround for now.
This issue really shouldn’t be closed, it causes a huge amount of chaos and needs to be looked at.