jitsi_app_c0

Historia

paweldomas 54c36198d0 fix(mobile/call-integration): cleanup if leave takes too long The conference disconnection process is asynchronous which means there's no guarantee that there will be CONFERENCE_LEFT event for the old conference, before the next conference is joined. Because of that we can end up with two simultaneous calls on the native side which is not always supported. End the call on CONFERENCE_WILL_LEAVE to fix this corner case.		6 lat temu
..
audio-mode	audio-mode: don't change the mode unless there is no active conference	6 lat temu
background	feat(App): refactor App and split it into BaseApp and App	7 lat temu
call-integration	fix(mobile/call-integration): cleanup if leave takes too long	6 lat temu
external-api	feat(external_api): export sendEvent function	7 lat temu
full-screen	[RN] Remove unused code	6 lat temu
incoming-call	ref(app): move initialization into componentDidMount	7 lat temu
network-activity	ref: move all prop type declaration to flow	7 lat temu
permissions	Reorganize calendar access request flow	7 lat temu
picture-in-picture	Replace console with logger	7 lat temu
proximity	ref(mobile/proximity): convert middleware to a state listener	7 lat temu
wake-lock	ref(mobile/wake-lock): convert middleware to a state listener	7 lat temu