Question about how to use the self-managed mode on Android

[GabrielBermudez]

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

- Callkeep: 4.3.13
- React Native: 0.74.2
- iOS:
- Android:
- Phone model: Samsung A54

[appinDhaval]

Hello,
did you find any way to set up self managed mode on android?

thanks, in advance

[OrrinHatch]

did you find any way to set up self managed mode on android?

[Wellapos]

any update?

[matteolucinip]

Did you find a solution to not ask for the extra permissions?
I'm not an expert on Android development and struggling to figure out if it's actually impossible to use incoming calls notifications without prompting for those permissions or it's just because of how this library is setup

[matteolucinip]

If it's useful to anyone, I did get self managed mode to work using @notifee/react-native.
I setup CallKeep, then I when I receive a notification (Firebase) I add some listeners (important here is showIncomingCallUi) so that I can handle showing the incoming call and other events like answer/end. I'm using attaching the notification to a foreground service and adding a full screen intent to it (which is the custom incoming call screen).

For us the issue is that we need to ask for permissions that would confuse our users, but again I'm not even sure that what we want is actually feasible as navigating the Android documentation (and CallKeep's) is quite hard without a full native context.