I receive messages from my local Hub but not messages via Azure SignalR service about signalr

[ryancole]

Holy cow, I just figured it out. I've been at this for about a week and a half now.

In the binding, when you specify hub name, you have to append hub to the name. I noticed that the @aspnet/signalr JS client was appending hub to the end of the name of my hub that I specify on the browser side of things. In my Functions binding, if I manually add hub to the end of my actual hub name, it works.

I must be doing something out of the ordinary though because I saw no mention of this anywhere, and none of the sample projects seem to do this. I'm unsure what the difference between what I'm doing is, though. I haven't seen any samples of using a local ASP.NET Core SignalR server with Azure SignalR service and Azure Functions. All the Azure Functions samples I've seen go the serverless route, and so I've not yet seen a sample exactly like mine - maybe that's where the difference lies?

[ryancole]

Oh no I see. It's taking the name of the hub from the class name. I don't know why I for some reason thought my hub was named "Functions" but my class is "FunctionsHub". Dang. A week out of the window due to that! haha

[BrennanConroy]

Glad you figured it out!