Cant transfer from Chrome to Chrome (Windows 10)

[ITCMD]

Can't tranfer from chrome to chrome, both on Windows 10 PCs. I am able to send to mobile devices, and then send from said mobile to PC.

Console log (sender):

Service Worker registered
manifest.json:1 Manifest: Enctype should be set to either application/x-www-form-urlencoded or multipart/form-data. It currently defaults to application/x-www-form-urlencoded
network.js:18 WS: server connected
network.js:27 WS: {type: "peers", peers: Array(1)}
network.js:27 WS: {type: "ping"}
network.js:27 WS: {type: "display-name", message: {…}}
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:27 WS: {ice: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:27 WS: {ice: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:328 ICE Gathering checking
network.js:310 RTC: state changed: connecting
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
3network.js:333 DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable
_onError @ network.js:333
(anonymous) @ network.js:289
Promise.catch (async)
onServerMessage @ network.js:289
_onMessage @ network.js:378
(anonymous) @ network.js:367
fire @ network.js:509
_onMessage @ network.js:39
ws.onmessage @ network.js:19
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
network.js:27 WS: {sdp: {…}, type: "signal", sender: "2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1"}
2network.js:333 DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable
_onError @ network.js:333
(anonymous) @ network.js:289
Promise.catch (async)
onServerMessage @ network.js:289
_onMessage @ network.js:378
(anonymous) @ network.js:367
fire @ network.js:509
_onMessage @ network.js:39
ws.onmessage @ network.js:19
network.js:328 ICE Gathering disconnected
network.js:310 RTC: state changed: failed
network.js:304 RTC: channel closed 2b732cc4-cf48-4e35-af9f-742469a3c64e; SLG_GWPT_Show_Hide_tmp=1; SLG_wptGlobTipTmp=1

Screenshot of same log:

Recipient log and screenshot in second comment.

[ITCMD]

Recipient console log:

Service Worker registered
network.js:18 WS: server connected
network.js:27 WS: Object
network.js:27 WS: Object
network.js:27 WS: Object
network.js:27 WS: Object
network.js:27 WS: Object
network.js:27 WS: Object
network.js:328 ICE Gathering checking
network.js:310 RTC: state changed: connecting
network.js:328 ICE Gathering disconnected
network.js:310 RTC: state changed: failed
network.js:304 RTC: channel closed c9a3e7fd-ea8a-4b05-a21b-125938a1ddc1
network.js:27 WS: {type: "ping"}

[ITCMD]

File Im uploading: (Honestly just posting here so I can download it on the other PC but maybe itll help):

[ThierryBegin]

exact same error here
-edit-
also tried on firefox, same issue, edges seem to work both at receiving and sending ends.
I was able to send a file from firefox to edge, not the other way around.
edge to edge works

[chiefnoah]

Same here between chrome on windows 10 and chrome on iOS.

[hariseldon99]

I'm having the same problem, I think, with a Samsung Galaxy A7 Lite (SM-T220) as recipient.

Error Message in Developer Console
network.js:333 DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable
_onError @ network.js:333
(anonymous) @ network.js:289
Promise.catch (async)
onServerMessage @ network.js:289
_onMessage @ network.js:378
(anonymous) @ network.js:367
fire @ network.js:509
_onMessage @ network.js:39
ws.onmessage @ network.js:19

Sender:

OS: ubuntu 20.04.3 LTS
Browser Chrome
Version 96.0.4664.45

Recipient

Device: Samsung Galaxy SM-T220
OS: Android 11 (One UI Core version 3.1) Kernel 4.19.127-22351182 Build No: RP1A.200720.012.T220XXU1AUJ1
Browser Chrome
Version 96.0.4664.45

[hariseldon99]

Update to my previous post:

On a hunch, I downloaded Firefox for Android from the Play store (version 95.2.0 build 2015851755 dt 2021-12-16) to my Samsung Galaxy SM-T220 and loaded snapdrop.net on there and it worked! Using firefox, I can talk to any other device on my wifi that is connected to snapdrop.net using any browser or app.

So, by the process of elimination, there must be something wrong with the config or build of chrome on the SM-T220 firmware. I'd welcome suggestions on how to probe this further (there is no about:config for chrome on android, right?)