Describe the bug
We have extended the DefaultNotificationHandler with our own implementation to customize the notifications.
The function of interest is getNotificationUpdates() where we get updates about the call and ringing state.
We noticed that when an incoming call is received while another call is already in progress (in active state), the function gets correctly triggered however the RingingState (accessible via call.state.ringingState) of the new call is Active instead of being Incoming. This happens only if there's another ongoing call open, if there's none the state is correctly Incoming.
Our custom implementation can be found here
SDK version
To Reproduce
Steps to reproduce the behavior:
- Start a voice call with user A (e.g., Andrea).
- While the call with user A is ongoing, receive a new call from user B (e.g., Karen).
- Put a breakpoint or log in
getNotificationUpdates to check the new call's call.state.ringingState
Expected behavior
- The ringing state of the call should be
RingingState.Incoming
Actual behavior
-
- The ringing state of the call should be
RingingState.Active
Device:
- Vendor and model: Google Pixel 9 Pro
- Android version: API 34
Describe the bug
We have extended the
DefaultNotificationHandlerwith our own implementation to customize the notifications.The function of interest is
getNotificationUpdates()where we get updates about the call and ringing state.We noticed that when an incoming call is received while another call is already in progress (in active state), the function gets correctly triggered however the
RingingState(accessible viacall.state.ringingState) of the new call isActiveinstead of beingIncoming. This happens only if there's another ongoing call open, if there's none the state is correctlyIncoming.Our custom implementation can be found here
SDK version
To Reproduce
Steps to reproduce the behavior:
getNotificationUpdatesto check the new call'scall.state.ringingStateExpected behavior
RingingState.IncomingActual behavior
RingingState.ActiveDevice: