Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bidirectional chat not working as expected #146

Open
Prabumca12 opened this issue Nov 2, 2020 · 7 comments
Open

bidirectional chat not working as expected #146

Prabumca12 opened this issue Nov 2, 2020 · 7 comments

Comments

@Prabumca12
Copy link

I'm able to connect hub but after there is no communication happened on bidirectional chat

image

@zackliu
Copy link
Contributor

zackliu commented Nov 13, 2020

Please uncheck send To Default Group: AzureSignalR because you're not in any group.
After you uncheck the checkbox, you can text something in textbox and press enter to broadcast

@Prabumca12
Copy link
Author

hi zackliu,

I have tried all the possibilities but not working for me and working only with negotiate (http trigger). I assumed signalr trigger not invoked. Is there any configuration missed me for my end?

image
image

@zackliu
Copy link
Contributor

zackliu commented Nov 19, 2020

If the trigger was totally not invoked (You can check it from Function's log), I assume the upstream settings in SignalR Service is not correct. And what's the browser console output when you try to send message? If there's no output, it seems to be the upstream setting is not set?
If you can't find out any reason, you can give me you ResourceID and time, I can check more from backend.

@Prabumca12
Copy link
Author

Prabumca12 commented Nov 19, 2020

There is no error in browser console and function log and find below SignalR Service settings. I'm assuming some settings from my end. Also, I'm not able to resourceID and time.

image

@zackliu
Copy link
Contributor

zackliu commented Nov 23, 2020

I checked the configuration of your resource, and found the upstream setting was empty. Please check the document to add the upstream setting. https://docs.microsoft.com/en-us/azure/azure-signalr/concept-upstream
For a quick setting and sample, see https://github.com/aspnet/AzureSignalR-samples/tree/chenyl/bi-direction/samples/BidirectionChat#deploy-project-to-azure-function
In the Upstream URL Pattern, fill in the <function-url>/runtime/webhooks/signalr?code=<signalr_extension-key>

@Prabumca12
Copy link
Author

Yeah you're correct. I missed that upstream setting. It's working fine. Is there any possibility to downgrade this project to .Net Core 2.2

@zackliu
Copy link
Contributor

zackliu commented Nov 24, 2020

It should work in 2.2, while you need to downgrade function tool from v3 to v2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants