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
Describe the bug
Moving from version 5.0.5 to 9.1.1, users connected to a MUC room do not leave the room anymore when the browser tab is closed. Thus, if they try to reconnect using the same nickname, they got the following error message:
The nickname you chose is reserved or currently in use, please choose a different one.
It is almost the same the configuration as for converse 5.0.5. I've just replaced the trusted: "off" option by allow_user_trust_override: "off", clear_cache_on_logout: true, and persistent_store: "sessionStorage" options.
Log in to an ejabberd 20.07 server, which is configured to accept websocket connection as anonymous users.
Log out (by closing the tab or changing the address).
Try to log in again with the same nickname.
Expected behavior
As keepalive is set to false, it should be possible to rejoin the same MUC room with the previous nickname, and it was working with converse 5.0.5.
Environment
Desktop
Chromium 101 and Firefox 100
Converse.js version 9.1.1
The text was updated successfully, but these errors were encountered:
I found out the issue : it is in the documentation. It says enable_smacks is by default at false but it isn't. Setting the enable_smacks option to false fixes my issue.
joudinet
added a commit
to joudinet/converse.js
that referenced
this issue
Jun 20, 2022
Describe the bug
Moving from version 5.0.5 to 9.1.1, users connected to a MUC room do not leave the room anymore when the browser tab is closed. Thus, if they try to reconnect using the same nickname, they got the following error message:
To Reproduce
Steps to reproduce the behavior:
It is almost the same the configuration as for converse 5.0.5. I've just replaced the
trusted: "off"
option byallow_user_trust_override: "off"
,clear_cache_on_logout: true
, andpersistent_store: "sessionStorage"
options.Expected behavior
As keepalive is set to false, it should be possible to rejoin the same MUC room with the previous nickname, and it was working with converse 5.0.5.
Environment
The text was updated successfully, but these errors were encountered: