react-native-webrtc / react-native-webrtc/react-native-callkeep

iOS: When Bluetooth device is available, incoming call defaults to receiver/earpiece when answered

Open
#614 5 comments 0 reactions 0 assignees View on GitHub

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

  • iOS

Description

When a BT device is connected, outbound calls will automatically connect to the BT audio route.

But for inbound calls, the audio gets routed to the receiver/earpiece instead of BT.

When I print out the events for RNCallKeepDidChangeAudioRoute, I receive a bunch of them once I answer the call. Sometimes they start off as BT, but it gets overrode by subsequent events showing receiver as the audio route. These events are triggered outside of my app.

Steps to Reproduce

Connect your device to BT device. Place an inbound call to CallKit app. Answer the call. Notice the audio route is not BT.

Versions

- Callkeep: 4.3.3
- React Native: 0.66.3
- iOS: 15.4.1
- Android: N/A
- Phone model: iPhone 11

Logs

Paste here

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked example and reproduce the inbound-call flow using a connected Bluetooth device on iOS. Observe the RNCallKeepDidChangeAudioRoute events after answering and compare them with the outbound-call behavior. Done means inbound calls retain the Bluetooth audio route instead of ending on the receiver/earpiece.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, react-native
Domain
audio-video-rtc, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.