react-native-webrtc / react-native-webrtc/react-native-callkeep
[Android] android 10 issue
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
when app is in background and if I call backtofreoground function if device unlocked app opens but if device locked then app not opening but it's work fine when app killed and device locked
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 Android 10 behavior described: compare calling backtofreoground while the app is backgrounded with the device unlocked and locked, including the case where the app is killed. Trace the Android entry point for backtofreoground and verify that the app opens while locked as well as when it is killed.
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
- Needs clarification
- Newbie friendliness
- 25/100