Closed LeonMarcel-HD closed 1 year ago
Thanks for the report, this is known and once fixed, I'll report back (TSCLIENT-3298).
I've another idea with the teamspeak.client_moved call. I'll implement in TS5SERVER-146 and it might not fix this exact issue but should make moves more robust in general as it puts the emphasis on the invite rather than expecting a successful leave (which sometimes might fail and then also the invite fails ATM).
Please try this again with the upcoming release after beta-58rc18. I've added a few changes with the teamspeak.client_moved code which creates the invite on the ts5client side for synapse.
I've checked again and it occurred only 1,2 times while switching ~80 times the channel. I think that it is working more reliable now.
It may be completely fixed as it happened only on the first few channel switches.
(I would reopen the issue if I find a way to reproduce it again)
The new feature is not even in yet. I'll post in this issue once it is. Thanks for your tests.
So it was not implemented in Beta-58rc20?
Yes, sorry for that. I'll report back once we have a release for this update.
@LeonMarcel-HD
From a teamspeak_server perspective this will be fixed with the upcoming beta-58rc22 ts-services release. If the problem persists afterwards please reopen.
Switching channels on a server too quickly sometimes results in being unable to read/connect to the channel chat. [Server beta-58rc8]