CODEWITHSUNDEEP
asp.netwpfsignalrsignalr.client
Sparrow_ua
Sparrow_ua

Reputation: 704

SignalR .NET client not firing events when network connection is lost

I have WPF application that connects to WebAPI, which runs SignalR. Everything works fine, until Internet connection is lost by client. When it happens, SignalR does not fire any events on client side (StateChanged, Error, Reconnecting, Closed etc.)

Code is pretty straightforward

 public HubConnection _hubConnection;
 IHubProxy _proxy;
 public async Task ConnectToHub(string hubUrl, string hubName)
 {
      _hubConnection = new HubConnection(HubURL);
      _hubConnection.Reconnecting += hubConnection_Reconnecting; 
      _hubConnection.Closed += _hubConnection_Closed;
      _hubConnection.StateChanged += _hubConnection_StateChanged;
      proxy = hubConnection.CreateHubProxy(hubName);

      await _hubConnection.Start();  

 }


   void _hubConnection_StateChanged(Microsoft.AspNet.SignalR.Client.StateChange obj)
    {
        throw new NotImplementedException();
    }

    void _hubConnection_Closed()
    {
        throw new NotImplementedException();
    }
    void _hubConnection_Reconnectig()
    {
        throw new NotImplementedException();
    }

SignalR version 2.2.0 Thanks for help

Upvotes: 1

Views: 2548

Answers (2)

Sparrow_ua
Sparrow_ua

Reputation: 704

Transport type on SignalR was set automatically to ServerSentEvents instead of WebSockets (Server admin didn't turn it on). Turned out that only with Websockets we can get connection-related events on .Net-client, when connection is lost.

According to http://www.asp.net/signalr/overview/getting-started/introduction-to-signalr

WebSocket is the only transport that establishes a true persistent, two-way connection between client and server.

Upvotes: 2

d.moncada
d.moncada

Reputation: 17402

Try subscribing to the Error event. Depending on "how" the connection is lost, I don't think some of the other events will get fired.

 _hubConnection.Error += (e=>{ ... });

Upvotes: 3

Related Questions