You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, the issue is correct. I rechecked it.
we can create this channel, but even admin cannot open it. Other user can leave it but not open it.
The channel . appears in the list, and backend operations like leaving the channel work, suggesting the database recognizes it
Clicking on the channel results in Page not found affecting both admins and users.
Likely cause: a routing issue where . is misinterpreted as a relative path in URLs or a validation gap allowing invalid channel names.
Description:
Channel called
.
can be created but it cannot be joined or returned after navigating away from it.Just a stupid issue we encountered, but nevertheless it is best to report it. It might indicate some other issue with escaping channel names etc.
Steps to reproduce:
.
with web clientExpected behavior:
You can join the channel as usual
Actual behavior:
In the url-bar the channel path shows as
/channel/
and not/channel/.
Typing in the correct url does not have any effect, as the address turns into /channel/ again.
Server Setup Information:
Client Setup Information
The text was updated successfully, but these errors were encountered: