react-native-callkeep icon indicating copy to clipboard operation
react-native-callkeep copied to clipboard

call will not display on IOS

Open imansalhi opened this issue 5 years ago • 11 comments

displayCall not working on IOS and no exception is provided(neither on real device nor emulator)... in android its necessary to get several access permissions but i dont see any permission access in ios installation docs? shall we get permission in IOS?

imansalhi avatar Jul 26 '20 09:07 imansalhi

It didn't work for me after ios 13.6. @manuquentin

CMLCNL avatar Jul 26 '20 16:07 CMLCNL

@imansalhi Did you setup VoIP properly in your project? We had a similar issue until VoIP was configured properly, then it worked fine in the latest iOS version (13.x)

whitmanc avatar Aug 28 '20 15:08 whitmanc

@imansalhi can you provide any logs?

danjenkins avatar Sep 07 '20 12:09 danjenkins

for me the native call UI is not displaying when i start call. The call is started though.

akshitrcrm avatar Dec 11 '20 07:12 akshitrcrm

@akshitrcrm did you get any solution for this? I'm also facing the same issue.

saranya20-t avatar May 07 '21 13:05 saranya20-t

Hello guys, someone know how to solve this, some configuration article available? Facing same issue here, use .startCall(...) but is like starting on background but never spawn the native Call screen and only way to end the call is force closing the app.

RobertoMenin avatar Jul 30 '21 15:07 RobertoMenin

experiencing same problems as https://github.com/react-native-webrtc/react-native-callkeep/issues/248#issuecomment-889980844

majirosstefan avatar Aug 28 '22 23:08 majirosstefan

+1

Mihai-github avatar Dec 21 '22 10:12 Mihai-github

I'm working on a new project, and I'm facing the exact same issue as others shared (like this comment)

If the app is closed (ie. not open or on iOS device on locked screen) the native Call UI is triggered, but if the app is close always goes to background and, for example, there is no way do end the call (besides force closing the app).

Is there any updates about this? Is there a workaround? If anyone could help we all would appreciate it for sure!

ssimoe50 avatar Jan 16 '23 15:01 ssimoe50

I am also experiencing this issue when initiating calls from within the app on ios. The calls are being placed but they run in the background, and the caller's name is displayed as "Default Contact." Has anyone else encountered and resolved this problem?

Are there any permissions required to do that on ios?

sakshya73 avatar Sep 14 '23 11:09 sakshya73

I am also experiencing this issue when initiating calls from within the app on ios. The calls are being placed but they run in the background, and the caller's name is displayed as "Default Contact." Has anyone else encountered and resolved this problem?

Are there any permissions required to do that on ios?

Hi @sakshya73, regarding the 'run in the background' part, I implemented a call ui within my app, so like this if app is closed it displays the native UI, if open (or opened while on the call) I display the in app call UI. Not the same thing, but well it works. Just a idea for you...

ssimoe50 avatar Sep 14 '23 20:09 ssimoe50