-
Notifications
You must be signed in to change notification settings - Fork 1
[_] bugfix/reconnection issues #182
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
base: main
Are you sure you want to change the base?
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
meet-web | 84cbf92 | Feb 10 2026, 03:20 PM |
| (conference, { dispatch }, previousConference) => { | ||
| if (previousConference) { | ||
| dispatch(toggleE2EE(false)); | ||
| if (previousConference && e2eeHandlerRefs?.conference === previousConference) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we even enter this without auto-reconnect?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It depends. In jitsi-lib, is the previous worker cleared if it reconnects to another conference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if conference called leave(), then yes. Else - no cleaning
|
Deploying meet-web with
|
| Latest commit: | 84cbf92 |
| Status: | ✅ Deploy successful! |
| Preview URL: | https://da33392a.meet-web.pages.dev |
| Updated (Europe/Madrid): | 10/2/2026, 16:15:00 |


Description
Related Issues
Related Pull Requests
Checklist
How Has This Been Tested?
Additional Notes