Open kenokenobingo opened 4 years ago
I've noticed the same too.
This is indeed an issue. I will look into it!
The issue isn't re-creatable with my local setup. I believe the reloads are caused by the WebRTC connection failing due to network issues and therefore reconnecting by reloading. In my local network the connection isn't failing though, most likely because the connection complexity is far lower than in a real-world scenario.
I'll have to run further tests between different networks, I'll see what I can do!
The issue isn't re-creatable with my local setup. I believe the reloads are caused by the WebRTC connection failing due to network issues and therefore reconnecting by reloading. In my local network the connection isn't failing though, most likely because the connection complexity is far lower than in a real-world scenario.
I'll have to run further tests between different networks, I'll see what I can do!
I don't think WebRTC will try reconnecting by reloading upon connection failure.
I don't think WebRTC will try reconnecting by reloading upon connection failure.
Not WebRTC itself, no. But this is the error handling implemented by the web client :)
For some reason, Zipcall reloads every few minutes at least on zipcall.io, disrupting the call. I don’t think this behavior is intended, is it?