Incorrect web socket management?

Hey @tommy

Thank you for the update.

1.8.5 sound likes it’s going to be fixed in months since 1.8.2 is still not there. As mentioned, i’m also interested in knowing where the problem is, not just that something is going to be fixed one day.
Depending on the root cause, this might be a critical fix (from our point of view), especially if it relates and causes this kind of other issue. (if it’s on web SDK side)

Do you have more details about the cause that you could share with us ?