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
This line logs a console.warn message when an action occurs in a state that does not support a transition for the given action. It will log this warning if an Update happens in the Disconnecting state:
No transition found from Disconnecting with Update
I suspect this warning is occurring frequently in our case because of the way we leave meetings:
This feels paranoid, but I am doing it because the documented way to end meetings is apparently incomplete, given further documentation that seems justified given my experience and also several stackoverflow questions on the topic [1], [2] (bottom answer is where I take my code from).
I have two questions:
Is the WARN level here correct? I can imagine situations where actions may happen concurrent with states for which there is no defined transition, and that being a benign situation.
What is the one true way to fully leave a meeting client-side in the way users would expect, without that logic creating console.warn messages in our logs?
Note: From my perspective as a user of this API , I do think fully leaving meetings (and releasing all employed resources) should be a single line of code. Perhaps I am missing something? But if not, the percentage of users who are googling in frustration after chapter 4 left their camera light running has got to be close to 100%.
The text was updated successfully, but these errors were encountered:
This line logs a console.warn message when an action occurs in a state that does not support a transition for the given action. It will log this warning if an
Update
happens in theDisconnecting
state:I suspect this warning is occurring frequently in our case because of the way we leave meetings:
This feels paranoid, but I am doing it because the documented way to end meetings is apparently incomplete, given further documentation that seems justified given my experience and also several stackoverflow questions on the topic [1], [2] (bottom answer is where I take my code from).
I have two questions:
console.warn
messages in our logs?Note: From my perspective as a user of this API , I do think fully leaving meetings (and releasing all employed resources) should be a single line of code. Perhaps I am missing something? But if not, the percentage of users who are googling in frustration after chapter 4 left their camera light running has got to be close to 100%.
The text was updated successfully, but these errors were encountered: