Impossible to reconnect in a MUC Room without to close the window/tab after a "You have been removed from the room due to technical problem"
Dear @psi-im team, @psi-plus team, @Ri0n, @Vitozz, @tehnick,
In some MUC Rooms, we can have:
[XX:XX:XX] *** Disconnected.
[XX:XX:XX] *** You have been removed from the room due to technical problem
After an XMPP Account session disconnection/reconnection in the Psi client, there is nothing because the MUC Room tab/window is blocked (text form is in grey).
We need to close the MUC Room tab/window and to reconnect manually in the MUC Room.
Linked to:
- https://github.com/psi-im/psi/issues/110
- https://github.com/psi-im/psi/issues/396
- https://github.com/psi-im/psi/issues/428
- https://github.com/psi-im/psi/issues/670
- https://github.com/psi-im/psi/issues/942
It is same when we are "kicked" from a room.
Same for:
[XX:XX:XX] *** Disconnected. [XX:XX:XX] *** Reconnecting... [XX:XX:XX] *** Unable to join groupchat. Reason: Unexpected request. The recipient or server understood the request but was not expecting it at this time (e.g., the request was out of order).
Same for:
[XX:XX:XX] *** Reconnecting... [XX:XX:XX] *** Unable to join groupchat. Reason: Conflict. Access cannot be granted because an existing resource or session exists with the same name or address.
If you are kicked out of the room, you cannot connect automatically. This is normal behavior. I propose to consider this ticket as invalid.
No, @Ri0n knows exactly the problem.
The mucroom window has a red cross and the text form is in grey, when we do a XMPP reconnection, the window is not refreshed.
It works after:
[XX:XX:XX] *** Disconnected. [XX:XX:XX] *** Reconnecting... [XX:XX:XX] *** Unable to join groupchat. Reason: Remote server not found. A remote server or service specified as part or all of the JID of the intended recipient does not exist.
In fact I can't reproduce it after kick. I didn't close the window, I just rejoined and it works again as expected.
rejoin after Disconnected works fine too.
@Neustradamus may be you use some old version.
I have tested in live with @Ri0n: he has seen a new time the problem.