Callkit loudspeaker bug / how WhatsApp fixed it?

Question

I have an app with Callkit functionality. When I press the loudspeaker button, it will flash and animate to the OFF state (sometimes the speaker is set to LOUD but

Answer 1

There is a workaround proposed by an apple engineer which should fix callkit not activating the audio session correctly:

a workaround would be to configure your app's audio session (call configureAudioSession()) earlier in your app's lifecycle, before the -provider:performAnswerCallAction: method is invoked. For instance, you could call configureAudioSession() immediately before calling -[CXProvider reportNewIncomingCallWithUUID:update:completion:] in order to ensure that the audio session is fully configured prior to informing CallKit about the incoming call.

From: https://forums.developer.apple.com/thread/64544#189703

If this doesn't help, you probably should post an example project which reproduces your behaviour for us to be able to analyse it further.

Answer 2

I've fixed the issue by doing following steps.

• In CXAnswerCallAction, use below code to set audiosession config.

  RTCDispatcher.dispatchAsync(on: RTCDispatcherQueueType.typeAudioSession) {
  let audioSession = RTCAudioSession.sharedInstance()
  audioSession.lockForConfiguration()
  let configuration = RTCAudioSessionConfiguration.webRTC()
  configuration.categoryOptions = [AVAudioSessionCategoryOptions.allowBluetoothA2DP,AVAudioSessionCategoryOptions.duckOthers,
                                   AVAudioSessionCategoryOptions.allowBluetooth]
  try? audioSession.setConfiguration(configuration)
  audioSession.unlockForConfiguration()}
  

• After call connected, I'm resetting AudioSession category to default.

  func configureAudioSession() {
  let session = RTCAudioSession.sharedInstance()
  session.lockForConfiguration()
  do {            
      try session.setCategory(AVAudioSession.Category.playAndRecord.rawValue, with: .allowBluetooth)
      try session.setMode(AVAudioSession.Mode.default.rawValue)
      try session.setPreferredSampleRate(44100.0)
      try session.setPreferredIOBufferDuration(0.005)
  } 
  catch let error {
      debugPrint("Error changeing AVAudioSession category: \(error)")
  }
  session.unlockForConfiguration()}
  

Thanks to SO @Алексей Смольский for the help.

Answer 3

Referd from Abnormal behavior of speaker button on system provided call screen

The same issue has been experienced in the previous versions as well. So this is not the new issue happening on the call kit. This issue has to be resolved from iOS. We don't have any control over this.

Please go through the apple developer forum

CallKit/detect speaker set

and

[CALLKIT] audio session not activating?

Answer 4

Maybe you can setMode to AVAudioSessionModeDefault.

When I use CallKit + WebRTC

1. I configure AVAudioSessionModeDefault mode.

2. Alloc CXProvider and reportNewIncomingCallWithUUID

3. Use WebRTC , after ICEConnected, WebRTC change mode to AVAudioSessionModeVoiceChat, then speaker issue happen.

4. Later I setMode back to AVAudioSessionModeDefault, the speaker works well.

Answer 5

Above answer is correct, "VoiceChat" mode ruin everything.

Swift 4 example for WebRTC. After connection was established call next

let rtcAudioSession = RTCAudioSession.sharedInstance()
rtcAudioSession.lockForConfiguration()
do {
    try rtcAudioSession.setCategory(AVAudioSession.Category.playAndRecord.rawValue, with: 
    AVAudioSession.CategoryOptions.mixWithOthers)
    try rtcAudioSession.setMode(AVAudioSession.Mode.default.rawValue)
    try rtcAudioSession.overrideOutputAudioPort(.none)
    try rtcAudioSession.setActive(true)
} catch let error {
    debugPrint("Couldn't force audio to speaker: \(error)")
}
rtcAudioSession.unlockForConfiguration()

You can use AVAudioSession.sharedInstance() as well instead RTC