From b2f884b8820a9c874d3b998618ba05cafdbaa192 Mon Sep 17 00:00:00 2001
From: Matthew Chen <matthew@signal.org>
Date: Fri, 25 May 2018 11:18:00 -0400
Subject: [PATCH] Fix call state edge cases.

---
 Signal/src/call/CallService.swift | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/Signal/src/call/CallService.swift b/Signal/src/call/CallService.swift
index 24604c805..4c6245ece 100644
--- a/Signal/src/call/CallService.swift
+++ b/Signal/src/call/CallService.swift
@@ -1233,10 +1233,9 @@ private class SignalCallData: NSObject {
         SwiftAssertIsOnMainThread(#function)
 
         guard let call = self.call else {
-            // This should never happen; return to a known good state.
-            owsFail("\(self.logTag) call was unexpectedly nil in \(#function)")
-            OWSProdError(OWSAnalyticsEvents.callServiceCallMissing(), file: #file, function: #function, line: #line)
-            handleFailedCurrentCall(error: CallError.assertionError(description: "\(self.logTag) call unexpectedly nil in \(#function)"))
+            // This can happen if you tap the video button right after the other
+            // user hangs up.
+            Logger.warn("\(self.logTag) ignoring local video change; no call.")
             return
         }