Closed
Bug 1067389
Opened 11 years ago
Closed 11 years ago
The call screen is not closed when trying to make a Loop call to a Busy user (already in another Loop call)
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: oteo, Assigned: jaoo)
References
Details
Attachments
(1 file)
Prerequisite: Users A and B have already established a Loop call
STR:
1)User C calls to user A
2)Second call can not be established, User C is notified that user A is Busy and busy tone is played
Expected Result: Call screen in C device is closed
Current Result: Call screen in device C is still open. We can not close it even pressing "hang up" button or closing and starting again the Loop application. Only after restarting the device, the call screen was closed
| Assignee | ||
Comment 1•11 years ago
|
||
Borja, we left a call to the former CallManager.stop() function. Would you review this 2-line patch please? Thanks!
Attachment #8489893 -
Flags: review?(borja.bugzilla)
Updated•11 years ago
|
Attachment #8489893 -
Flags: review?(borja.bugzilla) → review+
| Assignee | ||
Comment 2•11 years ago
|
||
Landed at:
https://github.com/mozilla-b2g/firefoxos-loop-client/commit/c6ae5aaa9a4a55388b1efa217f059865e91851b9
Thanks Borja!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Tested with Flame (v2.0 kk v180)
Gecko-9362b48.Gaia-6449cc3
Loop version 041ff17
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•