Track publication during reconnect not registered?

[SijmenHuizenga]

After updating the go server sdk from v2.3.1 to v2.4.1 we have seen the following regression:

The go application believes the track is published, but the web browser application does not see it.

These are the logs of the application:

2025-01-20 14:28:14	INFO	Livekit reconnecting    ( RoomCallbackOnReconnecting)
2025/01/20 14:28:14 "level"=0 "msg"="resuming connection..." "reconnectCount"=0
2025/01/20 14:28:14 "msg"="resume connection failed" "error"="reconnect received left, reason: STATE_MISMATCH"
2025/01/20 14:28:14 "level"=0 "msg"="restarting connection..." "reconnectCount"=1
2025/01/20 14:28:14 "level"=0 "msg"="published track" "name"="audio" "source"="MICROPHONE" "trackID"="TR_AMfaNXURDXiJDU"
2025-01-20 14:28:14	INFO	Livekit reconnected     (RoomCallback OnReconnected) 

Browser:

I tried refreshing the browser to no effect.

Room: RM_HwAZcbJjDucX