We have been successfully using signalR in our application. We recently upgraded to version 4 .0 here: 683de.... After that we are getting this javascript error:
VM41:1 GET http://localhost:5000/signalr/start?transport=webSockets&clientProtocol=1.5…22abpcommonhub%22%7D%2C%7B%22name%22%3A%22chathub%22%7D%5D&_=1493234804063 500 (Internal Server Error)
Are there any known issues with using signalR with the latest version?
5 Answer(s)
-
0
Hi,
Could you explain it a bit more clearly about following? In title you said "signalr error after upgrade to 2.0.x" and in body you said "We recently upgraded to version 4 .0"
Do you mean that you use aspnet-zero 4.0 and ABP 2.0.x?
-
0
Hello,
I apologize for the confusion, but yes. To be precise, we updated to the latest version of the "dev" branch in ASPNetZero here: https://github.com/aspnetzero/aspnet-zero/commit/683de0612490f512be79af464ec87e6f5e1bf3b6
Thank you for your help.
-
0
There is no change, except upgrading ABP versions in this repository. <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero">https://github.com/aspnetzero/aspnet-zero</a>
Could you look at Logs.txt file and send us if there is an detailed error in file? Normally, aspnet-zero does not run http://localhost:5000, are you running your project in release mode? And could you try it in debug mode?
-
0
Hello,
Thank you for your reply. This issue was caused by a number of factors:
- We had development databases with the simpleStringCipher issue here:https://github.com/aspnetboilerplate/aspnetboilerplate/pull/2071/commits/7cf02f9362f9067052f83a30d81490758659d76c. So to easily correct this, we deleted and recreated our host database.
- We forgot to add the friendships and appchatmessages tables from this issue https://forum.aspnetboilerplate.com/viewtopic.php?f=5&t=3892&p=8739#p8739
- When that error happens and we are running in debug mode but with "start without debugging" (also known as ctrl-F5 instead of just F5 in visual studio) then we do not see the error from #2 above, but get the signalR error in javascript.
This is not a problem with the upgrade. If it is possible to add better error handling for this situation, we would be be very grateful.
Thank you.
-
0
Hi,
We are glad that it is working for you now. We will think of this, showing error messages in a better way for next releases.
Thanks.
