Open fromtheredTH opened 1 month ago
same thing
Hello everyone I have the same problem Has anyone done this. I need help please;
I encountered this issue myself and did some investigating. I found that calling the following method in Dart causes the call to be answered twice:
FlutterCallkitIncoming.setCallConnected(uuid);
The conflicting code within the plugin is:
func connectedCall(call: Call) {
let callItem = self.callWithUUID(uuid: call.uuid)
callItem?.connectedCall(completion: nil)
let answerAction = CXAnswerCallAction(call: call.uuid)
let transaction = CXTransaction(action: answerAction)
callController.request(transaction) { error in
if let error = error {
print("Error answering call: \(error.localizedDescription)")
} else {
// Call successfully answered
}
}
}
I believe that the plugin utilises reportIncomingCall which does not allow for the user to set the connected state from what i have read? In the plugin example above constructing the answerAction
seems to be firing the accept call logic again and causing unpredictable behaviour.
Please try removing setCallConnected and see if this fixes your issue.
gating same issue please help to resolve it, before 4 month it was working fine
same issues
setCallConnected
i have not used this function (setCallConnected)
I discovered a bug that declined when I accepted a call from the other party in the iOS foreground.
Problem situation analysis When press accept, the callkit event call Event.actionCallDecline, but the problem is that the Event.actionCallAccept also comes in later. The same goes for click decline situations.
After the call kit event is first called Event.actionCallDecline, it is called again in the Event.actionCallDecline. -> Whether you press decline or accept, Event.actionCallDecline is always called first. (iOS only)
Since the pop-up is turned off no matter which of the callkit options is selected on iOS, isn't decline always called once?