Closed johanhelsing closed 6 months ago
I think I've noticed similar instances of failure but couldn't find a reproducible method and figured it was in my codebase, not matchbox. Interesting.
I tried deploying the server (the native "peer" is a server), and then connections were successful. So perhaps related to both peers being behind the same NAT.
I'll test this later.
I'm on Mac Ventura 13/Newest FF
I am unable to reproduce. Connected native client and then firefox client. @johanhelsing
Perhaps it only affects windows?
Update @johanhelsing ?
Yeah, this is now working for me
Did you do anything to make it work on Windows ?
No, it just suddenly started working, might be anything from webrtc updates os update, browser update. Hard to tell
Cross-play appears to be broken in this very specific case.
To reproduce:
cargo run -p matchbox_server
cargo run -p bevy_ggrs_example
cargo run -p bevy_ggrs_example --target wasm32-unknown-unknown
and open http://127.0.0.1:1334 in FirefoxConnection is never established.
Environment
Tested revisions
Additional details
It doesn't happen with Native and Chrome on the same system.
It doesn't happen if the browser connects to the signaling server first.
Both peers were on the same local network, behind NAT. Connections were sucessful happen when connecting to a native peer outside the NAT.
Logs
Firefox
Native