Issue when peer got reconnected after disconnected by using webrtc provider about y-webrtc HOT 6 OPEN

I am seeing similar issues. I have an app running on Edge and Chrome on one Win10 PC and Chrome on a Chromebook. All are using the WebRTC provider with the default signaling servers. And the IndexedDb provider.

Initially an update on a Browser was seen on the others, however now updates on Chrome on Win10 aren't seen on the other two Browsers. However the other two Browsers see each others changes. I've restarted the Win10 PC and this made no difference.

I've enabled webrtc logging and when I do an update on the Chrome + Win10 PC nothing is logged on the other two Browsers. Updates on the other two Browsers do show log entries on the other Browser.

Opening a second Chrome Tab in a second Chrome Window on the Win10 PC does show updates, but only from the other Win10 Chrome Tab.

If I delete all YJS content and .clearData() from indexeddb then all browsers communicate and update correctly again.

from y-webrtc.

Update: So I've done more trials using VM and turns out that sometimes the sync workflow works correctly, but sometimes it doesn't.

from y-webrtc.

hi, any update about this issue?

from y-webrtc.

I have also experienced this issue. What's more interesting, I'm using WebrtcProvider in conjunction with ProseMirror, and the cursor position won't get propagated after the connection has been lost and reestablished again.

from y-webrtc.

Any update on this?

from y-webrtc.

Oh I think this has been fixed in the last PR. Can you please test the latest version?

from y-webrtc.