Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong MediaStreamSettings after reconnection of WebSocket #149

Open
evdokimovs opened this issue Feb 14, 2024 · 1 comment
Open

Wrong MediaStreamSettings after reconnection of WebSocket #149

evdokimovs opened this issue Feb 14, 2024 · 1 comment
Assignees
Labels
bug Something isn't working enhancement Improvement of existing features or bugfix k::ui/ux Related to UI/UX experience

Comments

@evdokimovs
Copy link
Contributor

Summary

When WebSocket reconnection occurs for all users connected to the Room due to network-related lag on the server, the MediaStreamSettings of these clients may appear to be broken. Consequently, after the reconnection, device_video becomes disabled, and display_video becomes enabled, leading to screen sharing being activated for all users. This behavior seems to indicate a potential bug in our reactive state synchronization mechanism triggered during WebSocket reconnection through a full state update. However, certain aspects do not look related to this mechanism, so a more in-depth investigation needed.

Platform information

Not platform specific.

Steps to reproduce

  1. Start group call
  2. Members are connecting
  3. Network lag happens

What is the current bug behavior?

  1. Camera and microphone is disabled on every member now
  2. Screen-sharing is enabled on every member now (without user intention)

What is the expected correct behavior?

  1. All MediaStreamSettings should be the same as user selected before

Possible fixes

It looks like a problem in our state synchronization after WebSocket reconnection mechanism. So most likely bug is somewhere here, but firstly we need constant reproduce of this bug. We can trigger state synchronization on different stages of the call and try to catch this bug locally.

@evdokimovs evdokimovs added enhancement Improvement of existing features or bugfix bug Something isn't working k::ui/ux Related to UI/UX experience labels Feb 14, 2024
@evdokimovs evdokimovs self-assigned this Feb 14, 2024
@evdokimovs
Copy link
Contributor Author

@tyranron ,

Maybe you have some additions about this bug?

@evdokimovs evdokimovs assigned alexlapa and unassigned evdokimovs Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement Improvement of existing features or bugfix k::ui/ux Related to UI/UX experience
Projects
None yet
Development

No branches or pull requests

2 participants