react-native-webrtc / react-native-webrtc/react-native-callkeep
App not opened on answer after unlocking ios device
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
When the device is locked and there is any incoming call, i answered the call and then unlocked the screen but the application was in background state
Expected Behaviour: After unlocking the device it should be in the foreground state .
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
Reproduce the issue on an iOS device while it is locked, answer an incoming call, and then unlock it. Inspect the app's foreground/background handling around the call flow; done means the application returns to the foreground after unlocking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, 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