Answer / Reject callbacks not called when app is started by push

Bug report

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

• Reproduced on:

• Android

• [x ] iOS

Description

These callbacks are not called when the app starts from scratch due to a pushkit notification:

RNCallKeep.addEventListener('answerCall', this.onAnswerCallAction);
RNCallKeep.addEventListener('endCall', this.onEndCallAction);

As a result the app starts but no action is being taken in the javascript code to accept (or reject) the call.

This behaviour remains for as long as the app runs. The only way to get the callbacks called is to first start the app, then to get the incoming calls. The app can then be woken up from the background as well then using Push notifications, and the callbacks are called.

Steps to Reproduce

• Swipe the app out or restart the phone
• Make a call. The user accepts the call.
• The callback this.onAnswerCallAction() is not called

Versions

- Callkeep: nimbleape/react-native-callkeep-1#aaf508332ff0855f500bd522779ef87884b59621
- React Native: 0.61.5
- iOS: 12.x or 13.x
- Android:
- Phone model: Any

Logs

None

Reproduce the cold-start case by swiping out the app, triggering a PushKit notification, and accepting or rejecting the call. Trace the RNCallKeep.addEventListener registrations for answerCall and endCall through the iOS PushKit and CallKit startup path. Done means both JavaScript callbacks fire when the app starts from a push, matching behavior after the app has already been opened.