react-native-webrtc / react-native-webrtc/react-native-callkeep
EventListeners not registered if call received from voip push
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Bug report
-
I've checked the example to reproduce the issue.
-
Reproduced on:
-
iOS
Description
I am sending a voip push from my server to the app and when received, i am handling it from native side using
[RNCallKeep reportNewIncomingCall: ... ]
It shows the native UI for incoming call so I don't need to call RnCallKepp.displayIncomingCall(), but listeners are not working.
answerCall is never registered, i checked my logs endCall and didDisplayIncomingCall is working fine.
So my question is, it is necessary to trigger the native UI using RNCallkeep.displayIncomingCall() only to register the event listeners or is there any alternate way to register them even when the UI is shown from native side.
I am using react-native-voip-push-notifications to handle voip push.
Steps to Reproduce
Checkout this part https://github.com/react-native-webrtc/react-native-callkeep?tab=readme-ov-file#PushKit
Versions
- Callkeep: "^4.3.13",
- React Native: "0.74.2",
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the repository's README PushKit section and the iOS reproduction described in the issue. Compare the native reportNewIncomingCall flow with displayIncomingCall and trace how answerCall, endCall, and didDisplayIncomingCall listeners are registered. Done means the expected listener behavior is reproduced and either corrected or clearly documented for native VoIP push calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100