Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS 13 VOIP Background call is not working #345

Open
sushantgiri opened this issue Jan 13, 2020 · 12 comments
Open

iOS 13 VOIP Background call is not working #345

sushantgiri opened this issue Jan 13, 2020 · 12 comments

Comments

@sushantgiri
Copy link

Hello there,
I tested the application on iOS 12 it is working fine in all three states:

  1. App in foreground.
  2. App in back stack.
  3. App cleared from backstack.
    However in iOS 13 only App in foreground condition works. I do not receive any VOIP calls in background.

"On iOS 13.0 and later, if you fail to report a call to CallKit, the system will terminate your app. Repeatedly failing to report calls may cause the system to stop delivering any more VoIP push notifications to your app. If you want to initiate a VoIP call without using CallKit, register for push notifications using the UserNotifications framework instead of PushKit"

Please let me know if i have missed something or necessary changes that i have to make.

@gurpreet029
Copy link

Hello
Not sure if you have fixed this issue or not,
But for me
I have fixed by modifying some of the code
like whenever you receive a VoIP push, you have to trigger the call kit screen, because as of ios13 this is a necessary thing, and after this whenever the users accepts it will call didRecieveSession delegate and you have to just push to ur controller by accepting the call.

@raheeshishan
Copy link

Hello @gurpreet029 Can you send updated code Pushregistry

@tarikhs
Copy link

tarikhs commented Mar 18, 2020

Hello @gurpreet029 Just implement

func pushRegistry(_ registry: PKPushRegistry, didReceiveIncomingPushWith payload: PKPushPayload, for type: PKPushType, completion: @escaping () -> Void){
}

and report incoming call to callkit via reportNewIncomingCall and update the provided sample reportNewincomingCall to reportCall(with: uuid, updated: update)

@raheeshishan
Copy link

Hello @tarikhs

How to add incoming call update inside pushregistry.Iam using Objective-c and also how to get session inside push registry

@Rushang007
Copy link

@gurpreet029 can please share some code? how to trigger the call kit screen in iOS 13

@DineshKachhot
Copy link

DineshKachhot commented Jun 25, 2020

Hello @gurpreet029 Just implement

func pushRegistry(_ registry: PKPushRegistry, didReceiveIncomingPushWith payload: PKPushPayload, for type: PKPushType, completion: @escaping () -> Void){
}

and report incoming call to callkit via reportNewIncomingCall and update the provided sample reportNewincomingCall to reportCall(with: uuid, updated: update)

Your answer helped me a lot, I was having an idea what I waned to do, but your answer sparked me how to do, thanks.

@parthsit
Copy link

parthsit commented Jul 7, 2020

hello @DineshKachhot @gurpreet029 did it work for iOS 13 background incoming call ?
Can you please share steps to do it or code ? It would be great help as I am stuck with it.

@gurpreet029
Copy link

Hi @parthsit
please follow the sample Quickblox provided
https://github.com/QuickBlox/quickblox-ios-sdk/tree/master/sample-videochat-webrtc-swift

They have fixed the ios13 background incoming call issue.

@parthsit
Copy link

parthsit commented Jul 8, 2020

Hello
Not sure if you have fixed this issue or not,
But for me
I have fixed by modifying some of the code
like whenever you receive a VoIP push, you have to trigger the call kit screen, because as of ios13 this is a necessary thing, and after this whenever the users accepts it will call didRecieveSession delegate and you have to just push to ur controller by accepting the call.

Hi @gurpreet029 could you please share your solution because I downloaded latest sample quickblox source code and still issue persists. It would be really great help if you could share your code snippet with me/us.

@silicus-kirankhalkar
Copy link

@parthsit @gurpreet029 @DineshKachhot

Hello,
I am facing problem from Android to iOS Video and Audio call when App have in the background and Kill mode.

  1. iOS to iOS calls
.
    a. when the app is in the foreground, calling functionality works smoothly.
    
b. when app is in the background, calling functionality works smoothly.

    c. when the app was killed/screen locked, calling functionality works but not smoothly.


  2. android to iOS calls
.
    a. when the app is in the foreground, calling functionality works smoothly.
    
b. when the app is in the background, calling functionality not working.

    c. when the app was killed/screen locked, calling functionality not working.


So please tell me how can I achieve calling functionality from android to iOS when my app is killed or in background.

@NomanUmar
Copy link

Anyone found solution to show call view on background

@TappChat-dev
Copy link

@parthsit @gurpreet029 @DineshKachhot

Hello,
I am facing problem from Android to iOS Video and Audio call when App have in the background and Kill mode.

  1. iOS to iOS calls
 .
    a. when the app is in the foreground, calling functionality works smoothly.
    
 b. when app is in the background, calling functionality works smoothly.

    c. when the app was killed/screen locked, calling functionality works but not smoothly.
  2. android to iOS calls
 .
    a. when the app is in the foreground, calling functionality works smoothly.
    
 b. when the app is in the background, calling functionality not working.

    c. when the app was killed/screen locked, calling functionality not working.

So please tell me how can I achieve calling functionality from android to iOS when my app is killed or in background.

Can You help me for banchgroung and kill state in iOS -iOS and android - iOS .?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants