[BUG] Voice Calls fail to establish when account is logged in to more than 1 phone

[arcartis]

Code of conduct

• I have read and agree to adhere to the Code of Conduct

Self-training on how to write a bug report

• I have learned how to write a bug report

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have noticed that voice calls often fail to establish when the account is logged in to more than 1 phone and both are active. The voice call is then stuck at "5/6 Handling Connection Candidates".

Scenario:
Phone A and B are logged in to Account #1. Both are Google Pixel 7, one is stock Android, one is GrapheneOS.
Phone C is an Apple iPhone using Account #2.

When Account #2 on Phone C makes a call to account #1, phone A and B will ring immediately, so the notifications work. When accepting the call on phone A, phone B keeps ringing for a few more seconds. Then the Call between A and C are stuck at "Handling Connection Candidates".

When calling Account #2 on Phone C with Account #1 on phone A, it works fine, in my experience.
I tried in WiFi and 5G, no VPN or quirky things like Pi-Hole, etc. No VPN was active on the phones.

If more testing or logs are needed, I'm happy to provide these with specific tests.

Expected Behavior

When taking the call on either of the ringing phones, it should terminate the call for the other phone with the same account and establish the call with the phone that the user picked up with.

Steps To Reproduce

Log in to 2 phones with the same account (this was tested on Android, YMMV).
Get a friend / 3rd phone to call the account of the 2 phones.
Pick up on either of the phones, check if the call is established.
Observed behavior is, that the call establishment is stuck at either 4/6 Sending Connection Candidates or 5/6 Handling Connection Candidates.

Android Version

Android 16 (up to date)

Session Version

1.29.3 (4325 - a4a281)

Anything else?

No response

[ThomasSession]

Thanks for the report.
I've just run a few tests trying the scenario you described and never got any issues with it. I always managed to connect to the call (even when sometimes phone B took a while to realise the call was already accepted, it still always resolved into a working call).
The only difference in my tests is that none of the devices are running GrapheneOS, they are all on stock Android.
Can you maybe export the logs from the two phones receiving the call?
It's hard for us to try to fix this without being able to reproduce it.

[arcartis]

Hi,
thanks for the quick response. I don't know which way you prefer to receive the logs, but I raised a bug report via Helpdesk and referenced this Github issue, to which I uploaded the logs. If you like to have them in Github, let me know.
Helpdesk Ticket: #21340

I noticed, that when I pick up with the GrapheneOS phone, the issue cannot be reproduced, so it works just fine every time with that phone. It's only the stock Android Pixel 7 that is affected and only incoming calls, and only when the 2nd phone is also connected. Even after I wiped the local cache, uninstalled and reinstalled the app.

Honestly, this is probably an edge case, that I hit. I am most likely going to drop stock Android anyways. I would understand if you don't want to invest any more time into this. I will check if this also happens with the devices of a family member with a Samsung tablet and a smartphone. But that won't happen before Christmas.

In any case, thanks for looking into this.
Cheers

[ThomasSession]

Hi, thanks for the quick response. I don't know which way you prefer to receive the logs, but I raised a bug report via Helpdesk and referenced this Github issue, to which I uploaded the logs. If you like to have them in Github, let me know. Helpdesk Ticket: #21340

I noticed, that when I pick up with the GrapheneOS phone, the issue cannot be reproduced, so it works just fine every time with that phone. It's only the stock Android Pixel 7 that is affected and only incoming calls, and only when the 2nd phone is also connected. Even after I wiped the local cache, uninstalled and reinstalled the app.

Honestly, this is probably an edge case, that I hit. I am most likely going to drop stock Android anyways. I would understand if you don't want to invest any more time into this. I will check if this also happens with the devices of a family member with a Samsung tablet and a smartphone. But that won't happen before Christmas.

In any case, thanks for looking into this. Cheers

Thanks. I will check to get the logs from the helpdesk.
I think if it works with Graphene OS it means that stock Android is the one correctly handling the local hangup.
So the issue, it sounds like, is indeed GrapheneOS, because it's the one that might not be able to locally hangup when a connected device picks up the call.
I'll see if we can get info form the logs and will try to reproduce with a grapheneOS device.