he issue is that when internet connectivity is lost, the callState successfully transitions to .disconnected, but the CallComposite UI becomes unresponsive and freezes. Even if onDismissed is triggered or the leave action is initiated, the view remains stuck on the screen and fails to clear from the view hierarchy until the internal SDK signaling eventually times out.
he issue is that when internet connectivity is lost, the callState successfully transitions to .disconnected, but the CallComposite UI becomes unresponsive and freezes. Even if onDismissed is triggered or the leave action is initiated, the view remains stuck on the screen and fails to clear from the view hierarchy until the internal SDK signaling eventually times out.