Open
Description
I have implemented a Background Service using react-native-background-actions to keep the call active in the background, even if the user clears the app from recent apps during an ongoing call. This was working as expected.
However, after integrating CallKeep(in self managed mode) to display incoming call notifications (with android.permission.READ_PHONE_NUMBERS
granted), the app completely quits when cleared from recent apps, terminating the background service and disconnecting the call.
This issue seems to occur after implementing CallKeep, as the Background Service was working properly before.
Expected Behavior:
- The call should remain active even if the user clears the app from recent apps.
- The Background Service should continue running, ensuring the call persists.
Actual Behavior:
- After clearing the app from recent apps, the app fully exits, and the background service does not persist, causing the call to drop.
Steps to Reproduce:
- Start a call in the app.
- Ensure the background service keeps the call active when moving to the background.
- Clear the app from recent apps.
- Observe that the call is still active (before implementing CallKeep).
- Integrate CallKeep for incoming call notifications and request
android.permission.READ_PHONE_NUMBERS
. - Repeat steps 1–3.
- Notice that after clearing the app from recent apps, it fully quits, and the call disconnects.
Environment:
- Platform: Android
- React Native Version: 0.76.5
- CallKeep Version: ^4.3.14
- Device/OS: Oneplus Nord CE3, Android 14
Additional Notes:
- The issue started occurring only after integrating CallKeep.
- Possible conflict between CallKeep and the Background Service?
- Any insights on how to maintain the background service while using CallKeep would be helpful.
Metadata
Metadata
Assignees
Labels
No labels