-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onMuteToggle fails on page refresh #953
Comments
Hi, Could you provide more details on the steps you did to reproduce the issue? Also, which Streams version are you using for testing and could you share where you've placed your logic to subscribe to I did a quick test with the following code:
and everything was working as expected. The |
Hi, Sure, here are the steps:
We are using amazon-connect-streams version 2.18.0 As for code, we have the same as your example. I will share a bit more context for it though.
|
I see. One thing to note is that if you refresh the page while on a call, that call will be broken. If you refresh prior to being on a call, does the |
Yes |
We are using the following code and
onMuteToggle
fails when the page is refreshed.onEnqueuedNextState
works fine after a page refresh. We can see in the console log that mute events are still being received from amazon connect after the page refresh but code inonMuteToggle
is not triggering.if (connect) { try { connect.agent((agent) => { agent.onStateChange(() => { ... }) agent.onMuteToggle((agentMutedStatus) => {...}) agent.onEnqueuedNextState(() => {...}) }) } catch (err) {} }
The text was updated successfully, but these errors were encountered: