-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
failed WebSocket connection message when trying to use chat #9
Comments
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label. To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". For full info on how to contribute, please check out our contributors guide. |
Thanks for reporting this @jdwilkin4! The code is all good. The issue is that the Partykit portion of the site is not deployed. I encountered this while working on a project that uses this template. I'll get the partykit deployment sorted once I'm back from snowboarding. Also, if you'd like to be a maintainer, I'd love to have you on the team! No pressure, though. |
I've fixed the deploy but I still need to add the Partykit deployment as part of the deploy of the site. Closing this as completed as the bug no longer occurs. I will create a separate issue for adding partykit to the deployment. |
Love to be on the team 😄 |
Describe the bug
I tried using the chat by logging into a room with a username and when I go to that page, it won't submit a message. When I open up the console these are the messages displaying.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should be able to send a message
Screenshots
see screenshot above
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: