Reproduction steps
start Fluxer Desktop and sign in then join any voice channel while the microphone is muted. then you can hear other participants (audio arrives normally). then enable the microphone by clicking the mic button.
Expected behaviour
it would work as expected, everyone can hear me and i can still hear everyone.
Actual behaviour
webrtc connection is reset and then we reconnect in a loop, with mic on mute again.
Build information
Fluxer 2026.1117.144711
Electron 44.10.0
Chrome 152.0.7977.169
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Fluxer/2026.1117.144711 Chrome/152.0.7977.169 Electron/44.10.0 Safari/537.36
Platform: macOS 15.7.7 (arm64)
Platform
macOS
Evidence
i gathered the probable cause with the assist of agentic software. fluxer is not blocked on the network level: turn servers work ok, webrtc without my mic works ok.
no outbound audio ever appeared in the connection statistics after the failure. across five separate 30s captures, outbound RTP was 0 packets every time. the only outbound non-STUN frames were 997-byte control packets, 5 in 20 seconds
initial (join, muted) 7 offer / 7 answer mlines
after enabling mic 8 offer / 7 answer mlines, rejected
after failed negotiation back to 7 offer / 7 answer mlines
at join the app sets up 7 media sections that are three recvonly audio, three recvonly video, one data. the server answers with 7, the answer is accepted and the call works. when you turn the mic on, we add the mic by calling addTrack() and that doesn't reuse any of the three audio sections it already made and instead it creates a new section and appends it sendonly at the end.
the server answers with 7 anyway, webrtc requires the answer to have exactly the same sections in the same order as the offer, hence chromium refuses it with "The order of m-lines in answer doesn't match order in offer. Rejecting answer."
so the client then tries to recover by restarting ice which times out and shows up in the log as a ping timeout and a negotiation error.
Comments
No comments yet.