Skip to content

Wrong RingingState of incoming call during second ongoing call #1346

@soroa

Description

@soroa

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

  • 1.3.1

To Reproduce
Steps to reproduce the behavior:

  1. Start a voice call with user A (e.g., Andrea).
  2. While the call with user A is ongoing, receive a new call from user B (e.g., Karen).
  3. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions