@aspnet/signalr - Unable to receive a message sent to concrete client

[StanislavChankov]

Describe the bug

I am unable to receive a message sent from AspNetCore WebApi via Microsoft.AspNetCore.SignalR Hub to concretely targeted client.
The issue I am encountering exists only, when I am trying to send the message to single client:
await Clients.Client("Valid connection Id").SendAsync("Client message", response);

I am successfully sending the same message passing the same flow, when sending it to all of the clients:
await Clients.All.SendAsync("Client message", response);

To Reproduce

The code pictures are just examples of what I am trying to do.

Back-end AspNetCore side

Front-end Angular side

Further technical details

• ASP.NET Core version - netcoreapp3.0
• Node.js version - 10.16.3
• Angular version - 8.3.6
• aspnet/signalr version - 1.1.4
• Include the output of dotnet --info
  

• The IDE (VS / VS Code/ VS4Mac) you're running on, and it's version
  Microsoft Visual Studio Community 2019 - 16.3.5
  

[BrennanConroy]

First question I have to ask, how do you know you have a valid connection Id?

[StanislavChankov]

First question I have to ask, how do you know you have a valid connection Id?

Good question I could say. I am caching the connections to the memory cache and also logging the disconnected users via override Task OnDisconnectedAsync(Exception exception) method.

[BrennanConroy]

And you're using Context.ConnectionId from inside the Hub to get the connection ID initially?

[StanislavChankov]

And you're using Context.ConnectionId from inside the Hub to get the connection ID initially?

Exactly.

[BrennanConroy]

I can't think of anything that would be wrong from the info provided. Would it be possible for you to make a minimal repro app and put it on github?

[halter73]

If you send a message directly to Context.ConnectionId in OnConnectedAsync, does that work?

[StanislavChankov]

If you send a message directly to Context.ConnectionId in OnConnectedAsync, does that work?

@halter73, No. I am not able to send any message to anyone from OnConnectedAsync. I have tried Client(Context.ConnectionId), All, Caller, but isn't it expected behavior? I am not able to send any message from OnConnectedAsync in other hubs as well. I tried in other method sending a message to the same connection
await Clients.Client(Context.ConnectionId).SendAsync("method", new {});, but doesn't receive it.

I wrote an integration test, which shows exactly the same behavior. I am able to send a message, when I target all of the clients, but not able, when I select exact client. Therefore we are eliminating the possible issues in my client application and @aspnet/signalr library.

[StanislavChankov]

I can't think of anything that would be wrong from the info provided. Would it be possible for you to make a minimal repro app and put it on github?

@BrennanConroy, Is there a small app with netcoreapp3.0 with working example showing how to send private messages Clients.Client()

[BrennanConroy]

Sure, I created a super simple 3.0 app that sends to Clients.Client(Context.ConnectionId) in OnConnectedAsync.

https://github.com/BrennanConroy/3_0_Sample

[StanislavChankov]

Good job @BrennanConroy ! I have tested it and it is working perfectly. I created another branch in your repo, where I cached in the memory the connections in OnConnectedAsync and send the message to the other user in SendMessage and it is working properly.

I noticed that you are using @microsoft/signalr, which is created for AspNetCore. However I am using @aspnet/signalr as I have described above. I guess that's my mistake and switching to @microsoft/signalr@3.0.0 will fix the issue. One more thing, not only sending to concrete client, but also OnDisconnectedAsync is not working on @aspnet/signalr@1.1.4 with netcoreapp3.0

[BrennanConroy]

However I am using @aspnet/signalr as I have described above. I guess that's my mistake and switching to @microsoft/signalr@3.0.0 will fix the issue.

Using @aspnet/signalr shouldn't cause any issues. I switched the sample to @aspnet/signalr@1.1.4 and it continued working as expected.

One more thing, not only sending to concrete client, but also OnDisconnectedAsync is not working on @aspnet/signalr@1.1.4 with netcoreapp3.0

What isn't working? You probably wont be able to send a message to the specific client that is closing because it is in the process of shutting down.

Could you please provide a sample app that shows these things not working properly?

[StanislavChankov]

1. I had an issue with authorization. Exactly the same as ddydeveloper had in Authorize attribute doesn't work with SignalR ASP.Net Core 2.1 aspnet/SignalR#1764 . Hope that help to anyone.

            services
                .AddAuthentication("Bearer") // Just an example
                .AddJwtBearer(options =>
                {
                    options.Events = new JwtBearerEvents
                    {
                        OnMessageReceived = context =>
                        {
                            var accessToken = context.Request.Query["access_token"];
                            if (!string.IsNullOrWhiteSpace(accessToken))
                            {
                                context.Token = accessToken;
                            }

                            return Task.CompletedTask;
                        }
                    };
                });

2. I worked around the issue with Clients.Client(clientConnectionId) with Clients.User(staOpsConnections.Id). I guess I will come back, when I have to create a anonymous hub. I am sorry that I don't have enough time to provide you a sample repo of the issue.

@BrennanConroy , thank you one more time for taking the time to help me.

[ghost]

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!