Reported during QA session. Proposal, not a defect report.
What's wrong
When the callee accepts an incoming call, their call room briefly displays the "Calling…" state — the state meant for the caller who is waiting for someone to pick up. From the callee's point of view this is meaningless: they are the one who just answered, so nobody is being called.
The call room starts every session in the caller's initial state regardless of which side of the call the user is on, so the callee always passes through it on the way to connected.
What I expected
The callee should never see a "Calling…" state. Answering should move them from the incoming call screen straight into a connecting/answering state and then to connected.
Proposed change
Make the call room's initial state depend on the call direction: outgoing calls start in the calling state, incoming calls start in the answering state. Remove the calling state from the callee's path entirely rather than masking it with a shorter display.
Steps to reproduce
- Call device B from device A.
- On device B, accept the call.
- Watch device B's call room during the transition — the "Calling…" state appears before it connects.
Additional context
Worth doing alongside the Accept-button responsiveness work, since both concern what the callee sees between tapping Accept and being connected. Note that the caller-side spurious no-answer states are tracked separately — this issue is only about the callee's displayed state.
Reported during QA session. Proposal, not a defect report.
What's wrong
When the callee accepts an incoming call, their call room briefly displays the "Calling…" state — the state meant for the caller who is waiting for someone to pick up. From the callee's point of view this is meaningless: they are the one who just answered, so nobody is being called.
The call room starts every session in the caller's initial state regardless of which side of the call the user is on, so the callee always passes through it on the way to connected.
What I expected
The callee should never see a "Calling…" state. Answering should move them from the incoming call screen straight into a connecting/answering state and then to connected.
Proposed change
Make the call room's initial state depend on the call direction: outgoing calls start in the calling state, incoming calls start in the answering state. Remove the calling state from the callee's path entirely rather than masking it with a shorter display.
Steps to reproduce
Additional context
Worth doing alongside the Accept-button responsiveness work, since both concern what the callee sees between tapping Accept and being connected. Note that the caller-side spurious no-answer states are tracked separately — this issue is only about the callee's displayed state.