With ios 13, apple has changed the flow we handle voip incoming push notification.

Important On iOS 13.0 and later, incoming Voice over IP calls must be reported when they are received and before this method finishes execution using the CallKit framework, or the system will terminate your app. Repeatedly failing to report calls may prevent your app from receiving any more incoming call notifications.

pushRegistry(_:didReceiveIncomingPushWith:for:completion:)

I added new class method to report incoming call when there is new voip push

- (void)pushRegistry:(PKPushRegistry *)registry didReceiveIncomingPushWithPayload:(PKPushPayload *)payload forType:(NSString *)type {
  [RNVoipPushNotificationManager didReceiveIncomingPushWithPayload:payload forType:(NSString *)type];

  NSString *uuid = [payload.dictionaryPayload valueForKey:@"uuid"];
  NSString *callerName = [payload.dictionaryPayload valueForKey:@"fromUserName"];
  [RNCallKeep reportNewIncomingCall:uuid handle:@"hadle" handleType:@"generic" hasVideo:true localizedCallerName:callerName];
}

Implements support for running android in self managed mode. I've performed the implementation in a way that shouldn't change any behavior unless selfManaged is explicitly defined in RNCallKeep.setup():

 RNCallKeep.setup({
  android: {
    alertTitle: 'Permissions required',
    alertDescription: 'This application needs to access your phone accounts',
    cancelButton: 'Cancel',
    okButton: 'OK',
    imageName: 'iconmask',
    selfManaged: true, // <- Enables self managed mode
    additionalPermissions: [],
  },
});

I've purposely not added any changes to the documentation yet - I feel like it would be better to do so after we've decided on if we're going to take this PR.

Reviewing and Testing this PR It is anything but trivial to provide an example app for this, but I recommend performing these tests:

1. Verify that all functionality works as expected when selfManaged is NOT enabled.
2. In selfManaged mode, verify that showIncomingCallUi is fired in response to RNCallKeep.displayIncomingCall

The essence of this feature is just to make RNCallKeep deliver the showIncomingCallUi event to react native.

A summary of changes

1. Added showIncomingCallUi do the device emitter. This event is fired when the onShowIncomingCall() (link) method is called by android on the Connection implementation.
2. Adjust which permissions are required in RNCallKeepModule.java when running in selfManaged mode.
3. Changed index.js so it doesn't open phone accounts if running in selfManaged mode.
4. Added showIncomingCallUi event to index.d.ts

Marked in yellow in this diagram, is the only difference in operating principle of this module when running in self managed mode. At that point, responsibility of handling the UI related to the call falls entirely on the implementing app.

The app must still call all the relevant RNCK methods, and listen to the relevant events (such as end call, hold call etc.).

On an incoming call, we eventually execute RNCallKeep.displayIncomingCall(callUuid, callerNumber, callerName); - in turn, if Android deems this appropriate, it'll fire the showIncomingCallUi event, at which point we need code that shows a notification.

Anyway, let's discuss this wonderful feature!

Opinion piece on how this should be implemented: I can see from the other PR that was made for a feature - implementation is fairly similar to this one, that there's always talk about weather this works in background state, with the app dead, foreground etc, and I'd like to address some of that.

Firstly, there are my personal opinions, so we should of course talk about what we recommend for people implementing this.

But one prevailing fact remains, and that is that every app has individual implementation quirks around the sip stack, how it's implemented, what their infrastructure is capable of and all that - all of which means that this feature shouldn't be opinionated in nature.

Battling with stuff like background state, race conditions with initialization of the React Native bridge and so on, are all symptoms of a poor fit into an existing app and it's quirks.

Now on IOS, because of Apple's requirements to show the ring screen within (2?) seconds, all implementations should converge on doing everything in AppDelegate.m (see my other pull request on that).

However, on Android we're not as restricted (yet), but we should be prepared for that, and as such not impose a ton of opinion on the implementors.

But a requirements that FCM does have is that any high priority notification should result in a high priority notification, or they might deprioritize your messages. As such ANY high priority message should, no matter what, invoke RNCallKeep.displayIncomingCall(callUuid, callerNumber, callerName); asap - before even attempting to establish a SIP connection, and then deal with synchronizing this after the fact. And this is the part that'll be extremely different between apps.

My personal recommandation for implementation, is that people have their own implementation of firebase, that'll immediately launch a headless task in react native, that'll immediately invoke RNCallKeep.displayIncomingCall(callUuid, callerNumber, callerName); - and then start setting up the SIP connection, and converge these based on how the user interacts with the notification that's shown.

One important thing to know, is that the full screen notification can be done fully in react native - all of which will require some interaction with native android through the native bridge.

The headless tasks starts incredibly fast, and ensures that we launch the notification fast.

Libraries like react-native-notifications are unfortunately NOT appropriate for use together with these. They're a recipe for a poor implementation that'll make your apps ability to receive phone calls unreliable. They're too opinionated and hides away too much functionality.

Even on Android, doing something like this WILL require a fair amount of native implementation to achieve any degree of success. It simply won't work to operate only in React Native land for this.

A good example of what we're dealing with in other notification libraries, is that they all rely on an event handler to receive device tokens - and googles documentation is extremely clear on the fact that they can distribute a new device token at any point in time. A headless task is the only appropriate way to transport a device token to react native. Event handlers are NOT.

The immediate example that comes to mind is that Google distributes a new push token while the app is not running - there is no event bridge running, and no new token is stored. A headless task allows native to wake up enough of the react native app to deal with this.

Bug report

• [ ] I've checked the example to reproduce the issue.

• Reproduced on:

• [ ] Android

• [X] iOS

Description

When a call is resumed from a held state I am not getting audio back, unless I use InCallManager to toggle the device speaker.

Steps to Reproduce

• Place Call On Hold
• Hold Call
• Resume Call

Versions

- Callkeep: 3.0.6
- React Native: 0.59.10
- iOS: 12.4
- Android:
- Phone model: iPhone 8

After updating to 3.0.3 and updating my code to meet iOS 13 requirements so CallKit is reported from AppDelegate. But the problem is that when app is closed or in background, the callKit displays very fast before my call class get loaded. So the callKit is shown on screen before listeners are ready and if I accept or reject the call immediately nothing happened. I need to wait for 3 seconds until call listeners are ready then I can accept or reject.

How can I delay the callKit in AppDelegate until my call class is fully loaded?

UPDATE: This is now a feature request. Can react-native-callkeep be updated so that it can be used with setConnectionProperties(PROPERTY_SELF_MANAGED)?

Our use case is this: we have a cross-platform video chat app that uses opentok-react-native, and we currently use just push notifications to get users to pair with each other (using react-native-onesignal). When our users tap the push notification, they simply get dropped into our app.

We would instead want these video chat requests to look like phone calls. This means that we want the phone-call-esque screen to just act as a glorified push notification (tapping the answer button would trigger the exact same behavior that our push notification currently triggers -- opening the app, nothing more and nothing less).

It seems to me that such a functionality must be possible to do in CallKit and ConnectionService without all the other things that other typical VoIP apps need. For example, requesting the BIND_TELECOM_CONNECTION_SERVICE permission on Android shouldn't be needed, and it would be great to not have to show this to the user. (Or I may be misunderstanding ConnectionService.)

Is it possible to use react-native-callkeep as something like a full-screen push notification that just happens to look like an incoming phone call?

Support addition options can pass from js method

updateDisplay

original:

updateDisplay = (uuid, displayName, handle)

new:

updateDisplay = (uuid, displayName, handle, options = null) where the optional options could be:

{
  hasVideo: true,
  supportsHolding: true,
  supportsDTMF: true,
  supportsGrouping: true,
  supportsUngrouping: true,
} 

displayIncomingCall

original:

displayIncomingCall = (uuid, handle, localizedCallerName, handleType = 'number', hasVideo = false)

new:

displayIncomingCall = (uuid, handle, localizedCallerName, handleType = 'number', hasVideo = false, options = null) where the optional options could be:

{
  supportsHolding: true,
  supportsDTMF: true,
  supportsGrouping: true,
  supportsUngrouping: true,
} 

Note for API compatibility:

Originally, displayIncomingCallalready has hasVideo argument but updateDisplay are not. For api compatibility, I did NOT move displayIncomingCall.hasVideo inside displayIncomingCall.options

In the earlier time, we've exposed native reportNewIncomingCall and introduced an overloading function for the new payloadargument for api compatibility:

Earlier Original (as simple api):

[RNCallKeep reportNewIncomingCall:uuid handle:handle handleType:@"generic" hasVideo:false localizedCallerName:callerName fromPushKit: YES];

and

Earlier New (as full api):

[RNCallKeep reportNewIncomingCall:uuid handle:handle handleType:@"generic" hasVideo:false localizedCallerName:callerName fromPushKit: YES payload:extra];

We can't have too much overloading functions, so I keep the original one, and extend the new overloading function, so now is:

This PR Original (as simple api):

[RNCallKeep reportNewIncomingCall:uuid handle:handle handleType:@"generic" hasVideo:false localizedCallerName:callerName fromPushKit: YES];

and

This PR New (as full api):

[RNCallKeep reportNewIncomingCall:uuid handle:handle handleType:@"generic" hasVideo:false localizedCallerName:callerName supportsHolding: YES supportsDTMF: YES supportsGrouping: YES supportsUngrouping: YES fromPushKit: YES payload: payload];

TL;DR

For user using native RNCallKeep reportNewIncomingCall with payload argument should change to [RNCallKeep reportNewIncomingCall:uuid handle:handle handleType:@"generic" hasVideo:false localizedCallerName:callerName supportsHolding: YES supportsDTMF: YES supportsGrouping: YES supportsUngrouping: YES fromPushKit: YES payload: payload];

Hi,

I'm a little confused, I don't understand how to call this headless task, I tried push notifications but nothing was login in any console.

As I understand it automatically listens to the push notification when the app is killed but my function isn't triggering.

should I add any specific property in the push notification payload?

thank you in advance.

Hi,

My app works fine on iOS when the app is in background or foreground ho ever when app is in killed state then none of the event is getting called I am mainly interested in answerCall Event of RNCallKeep

Bug report

When Rejecting the Call On IOS

• Reproduced on:
• [ ] iOS 13

Description

When I get An Incoming VOIP Notification on IOS devices when App Is in Background mode, App Is Crashed Every time When I Reject the Notification. But Works Fine On Accept Call. And Working Fine On Foreground Mode For Both Accept and reject.

Steps to Reproduce

reject an Incoming call when app is in background

Versions

- Callkeep:3.0.9
- React Native: 0.58.6
- iOS:13.3.1
- Phone model: All

Logs Xcode Log

2020-02-13 12:12:19.305827-0500 555 Phone RN[3791:1852152] Apps receving VoIP pushes must post an incoming call (via CallKit or IncomingCallNotifications) in the same run loop as pushRegistry:didReceiveIncomingPushWithPayload:forType:[withCompletionHandler:] without delay. 2020-02-13 12:12:19.307019-0500 555 Phone RN[3791:1852152] *** Assertion failure in -[PKPushRegistry _terminateAppIfThereAreUnhandledVoIPPushes], /BuildRoot/Library/Caches/com.apple.xbs/Sources/PushKit/PushKit-37/PKPushRegistry.m:343 2020-02-13 12:12:19.307351-0500 555 Phone RN[3791:1852152] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Killing app because it never posted an incoming call to the system after receiving a PushKit VoIP push callback.' *** First throw call stack: (0x18463d80c 0x184365fa4 0x18453fc4c 0x1849756f4 0x19831ba5c 0x10241ebd8 0x10242d858 0x19831a9cc 0x10241d7fc 0x10241ebd8 0x10242cc34 0x1845bb3a8 0x1845b639c 0x1845b58a0 0x18e50d328 0x1886a6740 0x100646844 0x184440360) libc++abi.dylib: terminating with uncaught exception of type NSException

Google play store is rejecting me my app because I haven't requested READ_CALL_LOG permission. Is it required when using selfManagedMode? Calls are not currently registered anymore in the calls log.

I'm trying to solve the following problem: receiving an incoming call and displaying an incoming call window in the application, even when the application is killed.

I assume this is solved as follows:

1. High priority FCM message is sent to the Android 10 device (Pixel 2).
2. The App start the HeadlessJS task and call the RNCallKeep.displayIncomingCall function.

My FCM messages looks like this:

{
   "data":
		{
			"message":"New call",
			"sound":"default",
			"title":"New INVITE",
			"to":"[email protected]",
			"type":2
		},
    "priority":"high",
    "registration_ids": ["xxx"],
 } 

Implementation of FCM messages processing and display of an incoming call:

index.js

...
AppRegistry.registerHeadlessTask('RNFirebaseBackgroundMessage', () => bgMessaging);
...

bgMessaging.js

...
export default async (message: RemoteMessage) => {
   const options = {
        ios: {
            appName: 'MyApp',
            imageName: '../img/TabBar/contacts.imageset/contacts.png',
            ringtoneSound: 'my_ringtone_sound_filename_in_bundle',
            maximumCallGroups: '1',
            maximumCallsPerCallGroup: '1'
        },
        android: {
            alertTitle: 'Permissions Required',
            alertDescription: 'This application needs to access your phone calling accounts to make calls',
            cancelButton: 'Cancel',
            okButton: 'ok',
            imageName: 'sim_icon',
            additionalPermissions: [PermissionsAndroid.PERMISSIONS.READ_CONTACTS]
        }
    };

    RNCallKeep.setup(options);
    RNCallKeep.setAvailable(true);
   
    if(message.data.type==='2'){
            let _uuid = uuid.v4();
            RNCallKeep.displayIncomingCall(_uuid, "123", "123");
    }

    return Promise.resolve();
}

This works fine and the incoming call screen is displayed:

1. If the App has just been killed and the device display is still active.
2. If the App has just been killed and the device’s display has been blocked for a while.

This doesn't work or works with a long delay (about 60 sec after FCM received I see incoming call display) if the App was killed and the device’s screen was blocked and some time passed, for example 5 minutes. I think device in idle mode (Doze) in this moment .

What's wrong? How to make guaranteed to open the window of an incoming call after the arrival of a high-priority FCM-message in idle-mode (and inactive-mode) device?

Bug report

• [x] I've checked the example to reproduce the issue.

• Reproduced on:

• [x] Android

• [ ] iOS

Description

Building the project with react-native-callkeep fails on android

Steps to Reproduce

Android Manifest.xml

<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="app.trant"
	android:exported="true" xmlns:tools="http://schemas.android.com/tools">

	<uses-permission android:name="android.permission.INTERNET" />
	<uses-permission android:name="android.permission.CAMERA" />
	<uses-permission android:name="android.permission.MICROPHONE" />
	<uses-permission android:name="android.permission.RECORD_AUDIO" />
	<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
	<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
	<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
	<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
	<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
	<uses-permission android:name="android.permission.READ_CONTACTS" />
	<uses-permission android:name="android.permission.WRITE_CONTACTS" />
	<uses-permission android:name="android.permission.READ_CALL_LOG" />
	<uses-permission android:name="android.permission.BIND_TELECOM_CONNECTION_SERVICE"
		tools:ignore="ProtectedPermissions" />
	<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
	<uses-permission android:name="android.permission.READ_PHONE_STATE" />
	<uses-permission android:name="android.permission.CALL_PHONE" />
	<uses-permission android:name="android.permission.READ_CALL_LOG" />
	<uses-permission android:name="android.permission.BLUETOOTH" android:maxSdkVersion="30" />
	<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" android:maxSdkVersion="30" />
	<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />

	<uses-feature android:name="android.hardware.camera" />
	<uses-feature android:name="android.hardware.camera.autofocus" />
	<uses-feature android:name="android.hardware.audio.output" />
	<uses-feature android:name="android.hardware.microphone" />


	<application android:usesCleartextTraffic="true" android:name=".MainApplication"
		android:label="@string/app_name" android:icon="@mipmap/ic_launcher"
		android:allowBackup="false" android:theme="@style/AppTheme">
		<activity android:exported="true" android:name=".MainActivity"
			android:label="@string/app_name"
			android:configChanges="keyboard|keyboardHidden|orientation|screenSize|uiMode"
			android:launchMode="singleTask" android:windowSoftInputMode="adjustResize">
			<intent-filter>
				<action android:name="android.intent.action.MAIN" />
				<category android:name="android.intent.category.LAUNCHER" />
				<action android:name="android.telecom.ConnectionService" />

			</intent-filter>
		</activity>
		<service android:exported="true"
			android:name="io.wazo.callkeep.RNCallKeepBackgroundMessagingService" />
		<service android:exported="true" android:name="io.wazo.callkeep.VoiceConnectionService"
			android:label="Wazo"
			android:permission="android.permission.BIND_TELECOM_CONNECTION_SERVICE"
			android:foregroundServiceType="camera|microphone">

			<intent-filter>
				<action android:name="android.telecom.ConnectionService" />
			</intent-filter>
		</service>
	</application>
</manifest>

Versions

- Callkeep: 4.3.3
- React Native: 0.70.6
- Android: 12.0.0

Logs

/node_modules/react-native-callkeep/android/src/main/java/io/wazo/callkeep/RNCallKeepModule.java:367: Error: Call requires permission which may be rejected by user: code should explicitly check to see if permission is available (with checkPermission) or explicitly handle a potential SecurityException [MissingPermission]
        telecomManager.placeCall(uri, extras);

Bug report(Question?)

• [x] I've checked the example to reproduce the issue.

• Reproduced on:

• [ ] Android

• [x] iOS

Description

I've setup callkeep with APNs voip notifictaions and firebase notifications(for non-voip pushes) in an IOS app. When app is killed voip pushes are delived properly, the callkit screen is displayed and when user responds, they are navigated to the proper screen. However when app is active there's no sign of didReceiveIncomingPushWithPayload being called and when app is in the background, it crashes because apparently the completion method for voip pushes isn't being called.

Usually in the issues it's the other way around, as the killed app isn't being woken up properly, but here when the app is killed everything works fine. I'm not sure what's causing the issues but i guess it might have something to do with the fact that i'm using firebase notifications for other pushes, and that might be causing an issue for voip pushes.

I'm kinda stuck as to where to go from here and was wondering if someone can provide me with the reason behind this or a way to fix the issue

Thanks in advance😀

Steps to Reproduce

Versions

- Callkeep: 4.3.3
- React Native: 0.64.4
- iOS: 13
- Android:
- Phone model: Iphone 7, Iphone 6s

Logs

When app is in the background, the completion error for voip pushes is shown. when app is in the foreground, there doesn't seem to be any logs/responses, none of the event listerens are called in either situation.

Sample Code parts

// AppDelegate.m


// IOS push notificaion
// Required for the register event.
- (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
  [RNCPushNotificationIOS didRegisterForRemoteNotificationsWithDeviceToken:deviceToken];
  [RNNotifications didRegisterForRemoteNotificationsWithDeviceToken:deviceToken];

}
// Required for the notification event. You must call the completion handler after handling the remote notification.
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler
{
  NSLog(@"Native notificatoin recieved");

  // [RNCPushNotificationIOS didReceiveRemoteNotification:userInfo fetchCompletionHandler:completionHandler];
  [RNNotifications didReceiveBackgroundNotification:userInfo withCompletionHandler:completionHandler];

}
// Required for the registrationError event.
- (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
//  [RNCPushNotificationIOS didFailToRegisterForRemoteNotificationsWithError:error];
  [RNNotifications didFailToRegisterForRemoteNotificationsWithError:error];

}
// Required for localNotification event
- (void)userNotificationCenter:(UNUserNotificationCenter *)center
didReceiveNotificationResponse:(UNNotificationResponse *)response
         withCompletionHandler:(void (^)(void))completionHandler
{
  [RNCPushNotificationIOS didReceiveNotificationResponse:response];
}


- (void)pushRegistry:(PKPushRegistry *)registry didReceiveIncomingPushWithPayload:(PKPushPayload *)payload forType:(PKPushType)type withCompletionHandler:(void (^)(void))completion {
  NSLog(@"pushRegistry:didReceiveIncomingPushWithPayload:forType:withCompletionHandler:%@",
      payload.dictionaryPayload);

  NSString *uuid = [payload.dictionaryPayload valueForKey:@"call_uuid"];
   NSString *callerName = [payload.dictionaryPayload valueForKey:@"user"];
   NSString *handle = [payload.dictionaryPayload valueForKey:@"user"];
  
  [RNVoipPushNotificationManager addCompletionHandler:uuid completionHandler:completion];

  [RNVoipPushNotificationManager didReceiveIncomingPushWithPayload:payload forType:(NSString *)type];


  
  [RNCallKeep reportNewIncomingCall: uuid
                             handle: handle
                         handleType: @"generic"
                           hasVideo: YES
                localizedCallerName: callerName
                    supportsHolding: YES
                       supportsDTMF: YES
                   supportsGrouping: YES
                 supportsUngrouping: YES
                        fromPushKit: YES
                            payload: payload.dictionaryPayload
              withCompletionHandler: completion];

  completion();
  
}

// App.js

const CallKeepSetup = () => {
  const logger = useLogger('CallKeep');
  const navigation = useNavigation();
  const dispatch = useDispatch();

  const answerCall = ({ callUUID }) => {
    logger.info("Call recieved, answering call...")
    AsyncStorage.setItem('currentCallUUID', callUUID);
    try {
      logger.info("Starting Callkeep call")
      RNCallKeep.startCall(callUUID, 'Police', "Police", 'generic', true);
      logger.info("Call started successfully")
    } catch(e) {
      logger.error("Failed to start callkeep call")
    }

    setTimeout(() => {
      logger.info("Setting current active call...")
      try {
        RNCallKeep.setCurrentCallActive(callUUID);
        logger.info("Current active call set");
      } catch(e) {
        logger.error("Failed to set current call", {error: e});

      }
    }, 1000);
    logger.info("Call started successfully, setting active call")


    // On Android display the app when answering a video call
    if (!isIOS) {
      console.log('bringing app to foreground');
      RNCallKeep.backToForeground();
    }

    logger.info("Setting current call UUID")
    dispatch(setCurrentCallUUID(callUUID))

    logger.info("Navigating to call screen")

      navigation.navigate('Video Call');

  };

  const endCall = ({ callUUID }) => {
    logger.info("Ending call")
    
    try {
      dispatch(endCallWithUUID(callUUID));
      RNCallKeep.endAllCalls();
      logger.info("Call ended")

    } catch(e) {
      logger.error("Failed to end call", { error: e})
    }
  };

  const didDisplayIncomingCall = async ({ callUUID, payload, handle, }) => {
    try {
      logger.info('Recieved call with data', { payload, callUUID, handle });
      dispatch(
               startVideoChatWithouActivating({
          token: payload.token,
          room_name: payload.room_name,
          call_id: payload.call_id,
          friend: payload.friend,
          callUUID,
          call_uuid: callUUID,
          // location: JSON.parse(data.location ?? '{}'),
        })
      );
      logger.info('Call displayed with data', { payload, callUUID, handle });
    } catch(e) {
      logger.error('Failed to save call data', { payload, callUUID, handle });
    }
  }

  const handlePreJSEvents = (events) => {
    logger.info('PreJS events', { events });
    for (let event of events) {
      if (event.name == "RNCallKeepDidDisplayIncomingCall") {
        logger.info('PreJS events: didDisplayIncomingCall', { event });
        didDisplayIncomingCall(event.data)
      } else if (event.name == 'RNCallKeepAnswerCall') {
        logger.info('PreJS events: answerCall', { event });
        answerCall(event.data)
      } else if (event.name == 'RNCallKeepEndCall') {
        logger.info('PreJS events: endCall', { event });
        endCall(event.data)
      }
    }
  }

  const initializeCallKeep = () => {
    try {
      logger.info('Call keep initiated successfully');
      RNCallKeep.setAvailable(true);

      RNCallKeep.addEventListener('answerCall', answerCall);
      RNCallKeep.addEventListener('didReceiveStartCallAction', answerCall);
      RNCallKeep.addEventListener('endCall', endCall);
      RNCallKeep.addEventListener('didDisplayIncomingCall', didDisplayIncomingCall);
      
      if (isIOS) {
        RNCallKeep.addEventListener('didLoadWithEvents', handlePreJSEvents);
      }
    } catch (err) {
      logger.error('Failed to initialize call keep', {
        error: err,
        msg: err.message,
      });
      console.error('initializeCallKeep error:', err.message);
    }
  };


  useEffect(() => {
    initializeCallKeep();
    loadInitialCall();

    return () => {
      RNCallKeep.removeEventListener('answerCall', answerCall);
      RNCallKeep.removeEventListener('didReceiveStartCallAction', answerCall);
      RNCallKeep.removeEventListener('endCall', endCall);
      RNCallKeep.removeEventListener('didDisplayIncomingCall', didDisplayIncomingCall);
      if (isIOS) {
        RNCallKeep.removeEventListener('didLoadWithEvents', handlePreJSEvents);
      }
    };
  }, []);

  return <></>;
};

Hello everyone) After updating to the latest version of the program, there were a lot of crash reports with the following error:

Exception com.facebook.react.bridge.ObjectAlreadyConsumedException: Map already consumed
  at com.facebook.react.bridge.WritableNativeMap.putString
  at io.wazo.callkeep.RNCallKeepModule$VoiceBroadcastReceiver.onReceive (RNCallKeepModule.java:1158)
  at androidx.localbroadcastmanager.content.LocalBroadcastManager.executePendingBroadcasts (LocalBroadcastManager.java:313)
  at androidx.localbroadcastmanager.content.LocalBroadcastManager$1.handleMessage (LocalBroadcastManager.java:121)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:233)
  at android.os.Looper.loop (Looper.java:344)
  at android.app.ActivityThread.main (ActivityThread.java:8191)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:584)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1034)

Maybe someone also faced this problem?

• Reproduced on:
• [X] Android
• [ ] iOS

Versions

- Callkeep: ^4.3.3
- React Native: 0.63.5
- iOS: -

Here are some screenshots from google play console:

Bug report

Any suggestion for Incoming call notification full screen while lock screen state and notification popup awake the device. please help on this need to work both platforms. latest version of react native unable to support this feature. Please help on this. thanks in advance.

• Reproduced on:
• [ ] Android
• [ ] iOS

Description

Steps to Reproduce

Versions

- Callkeep:
- React Native:
- iOS:
- Android:
- Phone model: 

Logs

Paste here

Bug report

• [ v ] I've checked the example to reproduce the issue.

• Reproduced on:

• [ v ] Android

• [ ] iOS

Description

My app doesn't come up to foreground when I get a call with or without self-managed mode on foldable Galaxy models. In case of using self-managed mode, phone does just vibrate or ring but app is not opened in both of background state and completely closed state. Without self-managed mode, system call UI is shown, and when I answer the call, system call UI is still shown and app is not opened. These are happened only on Galaxy Z Flip and Fold series. I think backToForeground API is not working on these models.

Steps to Reproduce

Call Galaxy Z Flip or Fold user.

Versions

- Callkeep:4.3.3
- React Native:0.66.3
- iOS:
- Android:12
- Phone model: Galaxy Z Flip 3, Galaxy Z Flip 4, Galaxy Z Fold 4, ...

Logs

Paste here

Bumps qs from 6.7.0 to 6.11.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.