azure-signalr: SignalR Service client cannot receive messages after re-connect

I have a strange behavior that I don’t know what to do next…

I have a SignalRService connected to my appservice. I also have several clients (UWP app) that connect to SignalRService.

From those clients ~one~ some have this strange behavior. After the restart of the appservice, it succesfully connects to SignalRService and receives all the application messages sent by appservice. But if it reconnects to SignalRService, then from appservice it doesn’t receive any application messages sent to it. However it receives ping messages and is also capable of sending application messages

Message are sent like this: await m_Hub.Clients.Group(clientId).SendAsync("ServerToClientMessage", jsonSerializedMessage);

Please help!

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 24 (10 by maintainers)

Most upvoted comments

Closing this as we haven’t heard from you and generally close issues with no response after ~7 days. Please feel free to comment if you’re able to get the information we’re looking for and we can reopen the issue to investigate further!

vicancy on Aug 24, 2020

It is still unclear to me if the Default is one of the other 2 or not. I do not understand why you suggest to put it back on Default. Classic mode isn’t what I need (since I use an appservice)?

No, Classic mode is actually a mixed mode. You need ‘Default’ mode which prevents the Service from switching automatically to Serverless mode.

Is the client informed that will be connected to a serverless instance? How can I track that?

No. “Default” mode helps to prevent that silent switch.

We have a display bug in the portal which may lead to confusion is that: you init your instance and find out that your instance is in “Default” mode, however it actually behaves as “Classic” mode. You need to do a manual switch out and back to make it works as expect…

vicancy on Feb 21, 2019