Closed Bug 1083734 Opened 10 years ago Closed 10 years ago

[Loop] Incorrectly sending accept notifications to the websocket when a call is received.

Categories

(Firefox OS Graveyard :: Gaia::Loop, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1078315

People

(Reporter: standard8, Unassigned)

References

Details

(Whiteboard: [mobile app][blocking][tef-triage])

STR:

1) Sign in Firefox Desktop on nightly with an FxA account
2) Sign in the Hello app on Flame using the phone number
3) Either sign-in a second phone with a different FxA account, or sign in another Desktop with a different FxA account
4) Import a contact from Google Contacts that has the phone number of the flame and the email address of the FxA account
5) Start a call to that contact

Actual Results

- The call initiation starts, the Desktop UI shows "Connecting..." and "Ringing...", it then goes straight into showing an ongoing conversation, as if a call has been accepted.

- The Flame device and other FxA account are still showing the "Incoming Call" displays

Expected Results

- The desktop should have stayed as "Ringing..."


From looking at the logs, it appears the FxOS device is sending "accepted" to the websocket when the call hasn't actually been accepted.
Severity: blocker → major
I forgot to mention, I'm using latest master, revision c52321f9bb4d9ad2ade8b0d43ad719f8bae01972
Blocks: 1036490
Severity: major → critical
Whiteboard: [mobile app][blocking][tef-triage]
Blocks: 1078315
No longer blocks: 1036490
The patch on 1078315 solves this one too
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.