react-native-webrtc / react-native-webrtc/react-native-callkeep
[Android] - BackToForeground() sometimes does not work, and call remains in native UI
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
-
I've checked the example to reproduce the issue.
-
Reproduced on:
-
Android
Steps to Reproduce
Call android,
Press Accept on DropDown call UI
UI goes to native incall screen.
BackToForeground() does not return app to foreground
Versions
- Callkeep: latest
- React Native: latest
- Android: 7
- Phone model: Samsung S6
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
No source file or test is named. Start by reproducing the Android 7 behavior on the reported Samsung S6 using the listed call and Accept steps, then trace the Android handling of BackToForeground(). Done means the app returns to the foreground and the call no longer remains in the native in-call UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100