react-native-webrtc / react-native-webrtc/react-native-callkeep
After answering the call on MI note 7 pro, one more call notification is diplayed
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Bug report
- Reproduced on:
Android
Description
On MI note 7 pro, call notification is displayed twice, second call shows unknown caller. Second call is triggered when onAnswer is triggered.
Steps to Reproduce
- Set background handler in index js before App js
- Register for phone account after the notification is received
- Set call as available
- After that display incoming message
- In Appjs effect register the listener for the call answer
Versions
- Callkeep: 4.2.0
- React Native: 0.64.2
- Android: 10
- Phone model: MI note 7 pro
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 by reproducing the issue on Android 10 with the MI Note 7 Pro setup described, using the background handler in index.js and the listener in App.js. Trace the notification received, phone-account registration, call availability, incoming message, and onAnswer sequence. Done means answering the call produces only one notification and does not create an unknown second caller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100