psychollama / farnsworth Goto Github PK

I can't reproduce this myself, but when testing with other people (TE, ZG) the WebRTC session is successfully established, but one or both ends is black. Audio arrives just fine though.

I suspect the video.play() method.

I don't know why, but it seems consistent.

The getUserMedia(...) API just hangs. It never even prompts.

This happens on Android, Linux, and Mac. Only Chrome has this behavior. Firefox and Safari successfully query media devices.

If you try to dial someone and they try to dial you, it works, but there's a duplicate peer connection in state.

Scenario: you start and then stop sharing your screen. The track is closed locally and deleted just fine, but the remote peer isn't notified, and thus keeps the screen share view indefinitely.

This would be trivial to fix if track.onended fired, but that isn't how the browser works. I need to remove the track and detect a stream de-association through signaling: https://stackoverflow.com/questions/60636439/webrtc-how-to-detect-when-a-stream-or-track-gets-removed-from-a-peerconnection#answer-60860584

If you submit the invite form with an empty input, it blows up.

If you type a message into the chat input on mobile and press "Enter", it should send. And it does, but it requires you pressing it twice, and the first keypress registers as a newline. It's really weird.

Successful GUM queries loosen the autoplay policy. This does not extend to remote WebRTC tracks (otherwise advertisers would abuse it to death), so there's a race condition where receiving remote streams initialize paused unless you've already authorized GUM.

Farnsworth should wait for the GUM query to finish before initiating the call. (Even if it fails. You can still use chat.)

It shows the last frame of your webcam. I suspect the stream isn't getting cleared out properly, although I would expect browsers to handle that gracefully.

When Safari is forced into ICE rollback on a signaling conflict, it doesn't seem to take the hint:

InvalidStateError: Remote description type 0 is incompatible with current signaling state 1

I confirmed this only seems to happen when Safari is signaling in polite mode.

Source:

  handleAction(actions.tracks.add, (state, { peerId, track }) => {
    state[peerId].trackIds.push(track.id);
  }),

Repro (semi-consistent):

• Open two instances of the app
• From tab 1, connect to tab 2
• Refresh tab 2
• From tab 1, connect again

Tab 2 is frozen. The error shown above is thrown in the console.

This was a regression from 805dbf9. I need to filter on track sources in addition to kinds.

If you type a multiline message and hit send, it remains the same size until you start typing again. It should snap back to single line immediately.

I mirror all the local camera streams on your own display, but if you're using a phone, that's super trippy.