RNCallKeep is not working on app background and Inactive States

Bug report

• I’ve checked the(https://github.com/react-native-webrtc/react-native-callkeep/tree/master/example) to reproduce the issue.

Description

I have implemented RNCallKeep features in such a way that when a push notification arrives, then it tries to display an incoming UI through RNCallKeepDisplayIncomingUI(). When the app is in foreground as per the logic If I click on answer button, it is redirecting to a specific page; howsoever, the functionality that I am mentioning wasn’t working as expected when the app goes to background or inactive state.

In background state, on click of answer button, the expected behaviour is that app should change its state to foreground, open the app automatically and redirect to the specific screen. The navigation logic is working fine but it is not opening the app and behave according to the logic.

Help will be appreciated.

Versions

- Callkeep: 3.0.12
- React Native: 0.59.9
- iOS: 10.15.2
- Android: android 9.0
- Phone model: Nokia 5.1 plus 

[jason-shen]

Same here. Killed an app. Calling to this device — no reaction.

@pavanMude Figured out — need to configure, for example, Firebase background messaging (https://bit.ly/3ej3hoN — react-native-firebase v5 docs NOT THE LATEST, but just my case).

Then you need to register headless task.

AppRegistry.registerHeadlessTask(

  'RNFirebaseBackgroundMessage',

  () => CallMessagingManager.backgroundMessageHandler

)

Inside this backgroundMessageHandler it’s important to call methods:

RNCallKeep.setup(YOUR_OPTIONS)

RNCallKeep.setAvailable(true)

// rest of your call answer logic

After this at some moment (onAnswer, for example) you need to use something like that — react-native-invoke-app to return your app from background.

Just a question, This apply to android only right?

[nikolov9996]

RNCallKeep.setAvailable(true)

this part ended 2 days of suffering with RN a big TY!