You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x ] I've checked the example to reproduce the issue.
Reproduced on:
Android
iOS
Description
Good evening, I am trying to implement react-native-callkeep, but we encountered an issue where it requires the phone account permission, and on various phone manufacturers, it’s difficult to find where to activate the flag, which is concerning for the end user. We tried the self-managed mode, but we couldn’t get it to work; we don't fully understand how to implement it as the provided documentation is not very complete. Nevertheless, we appreciate the effort. Our idea is to receive a silent push notification, display a call alert even if the app is not open or the phone is locked, and upon answering the call, redirect the user to a screen with a two-participant room using WebRTC. If anyone could kindly provide advice on this topic, it would be much appreciated. Thank you very much.
Bug report
[x ] I've checked the example to reproduce the issue.
Reproduced on:
Android
iOS
Description
Good evening, I am trying to implement react-native-callkeep, but we encountered an issue where it requires the phone account permission, and on various phone manufacturers, it’s difficult to find where to activate the flag, which is concerning for the end user. We tried the self-managed mode, but we couldn’t get it to work; we don't fully understand how to implement it as the provided documentation is not very complete. Nevertheless, we appreciate the effort. Our idea is to receive a silent push notification, display a call alert even if the app is not open or the phone is locked, and upon answering the call, redirect the user to a screen with a two-participant room using WebRTC. If anyone could kindly provide advice on this topic, it would be much appreciated. Thank you very much.
Versions
The text was updated successfully, but these errors were encountered: