react-native-webrtc / react-native-webrtc/react-native-incall-manager
Speaker button's state is not correct in native call UI in iOS lock screen
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
Steps:
- Receiving call when the iPhone is in lock state.
- Slide to answer the call to display native call screen.
- Tap on Speaker button (the top right icon in the first row) to toggle speaker.
Expectation: it should show the right speaker state.
Actual: The speaker state is sometimes wrong such as it shows on speaker but actually not.
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 listed steps on an iPhone with the device locked, then inspect the native call UI and media-route handling for the speaker toggle. Done means the speaker button state consistently matches whether audio is actually routed through the speaker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- audio-video-rtc, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100