react-native-webrtc / react-native-webrtc/react-native-callkeep
Incoming call ui is not getting removed on accepting the call on mi devices(Android 11)
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 am using react-native-callkeep for displaying incoming call ui on receiving of firebase notification. We are able to display the ui.But on pressing accept button i am unable to hide the incoming call screen on some android 11 devices.
-
Reproduced on:
-
Android
Description
We are able to display the ui.But on pressing accept button i am unable to hide the incoming call screen on some android 11 devices.
Steps to Reproduce
`bgMessaging = async (message, ...props) => {
RNCallKeep.setup(options);
RNCallKeep.addEventListener('answerCall', async ({ callUUID }) => {
RNCallKeep.endAllCalls();
});
RNCallKeep.displayIncomingCall("uuid", "Display", "Display", "number");
}
return Promise.resolve();
}
AppRegistry.registerHeadlessTask('RNFirebaseBackgroundMessage', () => bgMessaging);`
Versions
- Callkeep:^4.2.0
- React Native:0.63.4
- Android: 11
- Phone model: Redmi note 9
Logs
Paste here
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 reported flow from the issue's Firebase background-message snippet on a Redmi Note 9 running Android 11, focusing on the answerCall handler and RNCallKeep.endAllCalls(). No source file or test is named; done means the incoming-call UI is removed after accepting the call on the affected device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, java, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100