iOS: Responding to incoming VoIP call when app inactive

Folgen

Rick LUPPINO

• 24. Juli 2022 14:20

When my app is inactive or has been killed and an incoming call is received, the native CallKit UI is displayed as expected. When I answer the call, the app is opened by the iOS operating system but the call is not properly established. I am listening for the didAddCall and didUpdateCall notifications but these don't seem to be caught.

What is the appropriate way to handle this use case i.e. where to catch the event that the app has been awakened by iOS due to a VoIP call being received and answered? I want to be able to catch this and open up my Video Call view controller.

0

• 

  Rick LUPPINO

  • 2. August 2022 23:38

  Further to the above, I can see in my device console logs that in the event that the app is killed, a call is received and the answer button on the CallKit UI is pressed, the call is actually not being answered at all (but my app is opened by iOS).

  Here is the relevant extract from my device logs.

  

  As the Rainbow SDK abstracts away all of the CallKit interaction, it appears that it is not answering (or not able to answer) the call. Is this a known issue or is there something that I am missing? I am initialising the Rainbow SDK in AppDelegate didFinishLaunchingWithOptions as per the documentation.

  Any insight on this issue and how to resolve it would be greatly appreciated.

  Thanks.

  0

  Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.