Post not yet marked as solved
Post marked as unsolved with 0 replies, 373 views
I'm running into an issue where performStartCallAction is never triggered if CXEndCallAction is called immediately after CXStartCallAction.
From what I've seen via documentation and device logs, starting and ending a call with CallKit will look like this:
A transaction with a CXStartCallAction is called
CXStartCallAction completion handler is called
performStartCallAction delegate method is triggered
...
Call continues and various other actions performed...
...
A transaction with a CXEndCallAction is called
CXEndCallAction completion handler is called
performEndCallAction delegate method is triggered
However, I've noticed that if the transaction with a CXStartCallAction is called and then a CXEndCallAction transaction is called before the CXStartCallAction transaction completes, the performStartCallAction delegate method never gets triggered and the app hangs. So rather than the above, this is what I see happening:
A transaction with a CXStartCallAction is called
A transaction with a CXEndCallAction is called
CXEndCallAction completion handler is called
App hangs...no further logs until I kill the app and restart
Why might this be happening? At the very least shouldn't I be getting some sort of error?