-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
feat(prejoin): fix join meeting from external/calendar link while in another meeting #15310
feat(prejoin): fix join meeting from external/calendar link while in another meeting #15310
Conversation
3cbb052
to
69f43e9
Compare
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.
I think the whole approach here is mcuh more complicated than it needs to be.
Where is the source of the problem, actually?
My hunch is that the Prejoin screen is cached, so not unmounted. As such, there is no code path that leads to calling setIsJoining(false);
is there?
So what we really need is to reset that state. I think we have options for that. One could be when we navigate away, that is, after navigateRoot
or perhaps when the component is blurred, but we do need to account for the warning screen. Another one is to do it when the room name changes, but there is a corner case when it doesn't, aka you try to join the same meeting.
Puttins this logic in the middleware is much more bug prone because we need to make sure all failure code paths cleanup.
bc87cd6
to
e24c397
Compare
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.
Pl squash-merge and explain thoroughly.
…another meeting (#15310) If you are in meeting and you want to join another meeting from an external link, it is not possible. That is because Prejoin screen didn't get unmounted, isJoining remains true and button is unpressable. Most probably because react navigation, where the screen only gets focused or blurred.
…nfig * mobile-24.6: (367 commits) feat(prejoin): fix join meeting from external/calendar link while in another meeting (jitsi#15310) chore(apps, version): bump to 24.6.0 chore(sdk, version): bump to 10.3.0 fix(connection): Detects tenant hyphen and length problems and show notification. fix(connection): Shows notification instead of reload on conference request failed. feat(conference): revert fix for background app state (jitsi#15308) feat(tests): First test from torture to meet. (jitsi#15298) lang: update German translation chore(deps) lib-jitsi-meet@latest fix(local-recording) handle repeated values fix(ci) use macOS 15 to run iOS tests Update main-tr.json feat(reactions): Added heart reaction feat(ns) update Krisp to latest version feat(Video): Handle .play() errors. tr language updates fix(visitors): Fixes detection of turning of subtitles by visitor. fix(base/icons): error regarding default props fix(prejoin): Device indicator. chore(deps) lib-jitsi-meet@latest ... # Conflicts: # android/gradle.properties # android/sdk/src/main/java/org/jitsi/meet/sdk/JitsiMeetOngoingConferenceService.java # ios/app/broadcast-extension/Info.plist # ios/app/src/Info.plist # ios/app/watchos/app/Info.plist # ios/app/watchos/extension/Info.plist # ios/sdk/src/Info.plist # ios/sdk/src/Lite-Info.plist # react-native-sdk/package.json # react/features/keyboard-shortcuts/actions.web.ts
I am not sure what was the reason behind that implementation, but I see no reason to keep it.
It breaks joining a meeting from external/calendar link while in another meeting.