Question: How to make it use iOS CallKit about twilio_voice HOT 12 CLOSED

from twilio_voice.

Yes, all certificates are are correct. I already have a (Swift) iOS app using the same Twilio server, and that is showing the CallKit UI correctly - I am trying to migrate this app to Flutter.

from twilio_voice.

well that's strange then, If you already know how to setup for native, Flutter is no different.
So you are already calling your server to register your user?

Maybe try running the flutter iOS project and debug the plugin, you should be receiving the "successfully registering for notifications" log

from twilio_voice.

Thanks...
I was indeed not getting the registered for remote notifications.
Annoyingly, a clean and rebuild of everything fixed that issue.

However, I'm now never receiving the "CallEvent.answer" event.
Any idea why?

from twilio_voice.

The answer event is only received by the callee, not the caller. (with default answer_on_bridge setting)
Is the call actually taking place?

from twilio_voice.

Yes, the call takes place, but neither caller or callee gets the CallEvent.answer event. Both get hangup event.

from twilio_voice.

Weird, can you check if you have the same bug running the example project?

from twilio_voice.

So here's a debug log (this is on iOS)

LOG|pushRegistry:didReceiveIncomingPushWithPayload:forType:completion:
flutter: pushRegistry:didReceiveIncomingPushWithPayload:forType:completion:
LOG|callInviteReceived:
flutter: voip-onCallStateChanged CallEvent.log
flutter: callInviteReceived:
Ringing|e613bb99_af6c_4afb_bc63_1909a19c8b92|client:11d3399a_47c1_42c6_ae60_9dcb20f908bf|Incoming
flutter: voip-onCallStateChanged CallEvent.log
flutter: Ringing - From: e613bb99_af6c_4afb_bc63_1909a19c8b92, To: 11d3399a_47c1_42c6_ae60_9dcb20f908bf, Direction: CallDirection.outgoing
flutter: voip-onCallStateChanged CallEvent.ringing
LOG|Incoming call successfully reported.
flutter: Incoming call successfully reported.
flutter: voip-onCallStateChanged CallEvent.log
[connection] nw_endpoint_handler_set_adaptive_read_handler [C5.1 52.21.15.69:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0, ipv4, dns)] unregister notification for read_timeout failed
[connection] nw_endpoint_handler_set_adaptive_write_handler [C5.1 52.21.15.69:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0, ipv4, dns)] unregister notification for write_timeout failed
LOG|provider:performAnswerCallAction:
LOG|performAnswerVoiceCall: answering call
flutter: provider:performAnswerCallAction:
flutter: voip-onCallStateChanged CallEvent.log
flutter: performAnswerVoiceCall: answering call
flutter: voip-onCallStateChanged CallEvent.log
flutter: Answer - From: e613bb99_af6c_4afb_bc63_1909a19c8b92, To: 11d3399a_47c1_42c6_ae60_9dcb20f908bf, Direction: CallDirection.incoming
flutter: voip-onCallStateChanged CallEvent.answer
LOG|provider:didActivateAudioSession:
flutter: provider:didActivateAudioSession:
flutter: voip-onCallStateChanged CallEvent.log
flutter: provider:didActivateAudioSession:
flutter: voip-onCallStateChanged CallEvent.log
flutter: CallEvent.log e613bb99_af6c_4afb_bc63_1909a19c8b92
Connected|client:e613bb99_af6c_4afb_bc63_1909a19c8b92|client:11d3399a_47c1_42c6_ae60_9dcb20f908bf|Incoming
LOG|provider:performAnswerVoiceCall() successful
flutter: Connected - From: e613bb99_af6c_4afb_bc63_1909a19c8b92, To: 11d3399a_47c1_42c6_ae60_9dcb20f908bf, StartOn: 2021-06-23 09:39:40.336905, Direction: CallDirection.incoming
flutter: voip-onCallStateChanged CallEvent.connected
flutter: Connected - From: e613bb99_af6c_4afb_bc63_1909a19c8b92, To: 11d3399a_47c1_42c6_ae60_9dcb20f908bf, StartOn: 2021-06-23 09:39:40.337722, Direction: CallDirection.incoming
flutter: voip-onCallStateChanged CallEvent.connected
flutter: provider:performAnswerVoiceCall() successful
flutter: voip-onCallStateChanged CallEvent.log
flutter: provider:performAnswerVoiceCall() successful
flutter: voip-onCallStateChanged CallEvent.log
flutter: ATG in switch:: CallEvent.log call from e613bb99_af6c_4afb_bc63_1909a19c8b92

As you can see, the TwilioVoice reports all the correct stages of the call, but those events are not being received by the running Flutter app while the CallKit UI is active, in the 'switch (event)'. As soon as the call is accepted (and the CallKit ui has gone), then the Flutter app receives the events eg the debug 'flutter: ATG in switch:: CallEvent.log call from e613bb99_af6c_4afb_bc63_1909a19c8b92'

This means there is no way of retrieving the id of the caller until the call is answered.
Is this expected behaviour?

from twilio_voice.

Hi, thanks for your help so far.
I now have iOS working.

On Android, I can make and receive calls, but the identity of the caller is not shown

The Twilio_voice logs show 'null' as the 'to' and 'from'. Is there any extra initialisation that should be done?

I/flutter (18065): Ringing - From: null, To: null, Direction: CallDirection.outgoing
I/flutter (18065): voip-onCallStateChanged CallEvent.ringing
I/flutter (18065): Ringing - From: null, To: null, Direction: CallDirection.outgoing

from twilio_voice.

Hi, I think there was an issue for Android that I recently fixed, let me see if I'm missing a commit

from twilio_voice.

I have submitted the fix on 0.0.7, if it is still not fixed, check that the posted params on your server are the ones you expect.

from twilio_voice.

Closing this for now, if there are any further issues pleas feel free to reopen this or open a new one

from twilio_voice.