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
The livechat agent in a conversation shall be pictured (literally) in the livechat-header of the client. This is not the case with guest-pool configured.
Steps to reproduce:
Configure livechat with guest pool
Open a client session
Send a message from the client
Pick the inquiry from the queue
Expected behavior:
The agent joined shall be shown in the client header
Actual behavior:
Only, once the client refreshed the browser, the agent's data is shown
Server Setup Information:
Version of Rocket.Chat Server: 0.70.4 && develop
Additional context
I have done quite some intense research on this issue.
I debugged / traced, that
the event agentData is properly emitted
the autorun in the client (_livechat.js) runs once on initialization, but no more once the agent joins
the streamer event handler function (this.stream.on) is never executed
the room ID which is used as the key for the streamer is the same for the emitted and listened-on-event
Description:
The livechat agent in a conversation shall be pictured (literally) in the livechat-header of the client. This is not the case with guest-pool configured.
Steps to reproduce:
Expected behavior:
The agent joined shall be shown in the client header
Actual behavior:
Only, once the client refreshed the browser, the agent's data is shown
Server Setup Information:
develop
Additional context
I have done quite some intense research on this issue.
I debugged / traced, that
agentData
is properly emitted_livechat.js
) runs once on initialization, but no more once the agent joinsthis.stream.on
) is never executedI added a patch with all logs and some other helpless tries I added, for convenience if it may help
I have seen that the streamer has undergone quite some changes on Oct. 24, so I at least can imagine that it may be an issue in the lib.
The text was updated successfully, but these errors were encountered: