Open GerryFudd opened 7 years ago
Hi,
Are you expecting it when you decline the call from the user who is getting the call, or when you are cancelling the call from the person who is sending the call?
I think it may only occur when the call invite is canceled by the caller - let me know if that isn't working.
I am expecting the event when I receive the call through CallKit. If it only fires when the caller hangs up, then that explains why the event doesn't fire.
It would be useful to have an event that fires when I hang up from CallKit (is this possible?)
Call did disconnect should fire - would that work?
That should work.
I just checked. I'm not getting call did disconnect either. I'm assuming call did disconnect only fires if the connection is established initially. This use case is that the app user rejects an incoming call rather than answering.
Consider this a low priority ticket by the way. If you have other tasks that you're already planning on getting to, don't worry about this one for now.
It's more of a thing that would be nice to have rather than something that's imperative.
This is most likely fixed with the latest PRs on master. @jefflinwood
I just received a call and declined it a number of times. I don't see the log that should come from
NSLog(@"Call Invite Cancelled: %@", [callInvite description]);
.Also (unsurprisingly) the callback that I submitted to
callinvitecanceled
doesn't run after I decline a call.