Closed Bug 1127314 Opened 11 years ago Closed 11 years ago

Call screen frozen when user joins to the Room via Standalone UI and default mode is set to Audio

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: oteo, Assigned: crdlc)

References

Details

(Whiteboard: [Room1.1.1_Exploratory1][loop approved for 1.1.1][In 1.1.1])

Attachments

(1 file)

I am seeing this issue in master and 1.1.1 branches of Loop Mobile Client Prerequisites: User A and B logged in Loop Mobile app. User A has created and shared a room URL with user B via SMS or E-mail STRs: 1. User B sets Default Mode:Audio in Loop Settings. 2. User B clicks on the received Room URL 3. StandaloneUI is open and user B click in "Join" button. 4. User B is joined to the Room via Loop Mobile app 5. User B leaves the Room 6. User B repeats again steps 2,3,4 and 5 to join the Room by tapping the room URL (no via Loop application) Actual result: User B can not the leave the Room, buttons do not repond and it's necessary to kill and relaunch the app to continue using it. Expected result: User B can leave the Room, tapping in the hang up button. Note: After this error happens, when I restart the application and try to join to the Room in devide B, a general error is shown and after that, the frozen call screen is shown again.
Whiteboard: [Room1.1.1_Exploratory1]
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Severity: normal → critical
See Also: → 1127386
Not sure, but perhaps this issue can be related to the one reported in bug 1127386
Attached file Github pull request
Attachment #8556982 - Flags: review?(josea.olivera)
Attachment #8556982 - Flags: feedback?(oteo)
Comment on attachment 8556982 [details] [review] Github pull request LGTM, r=me Nice way of fixing the issue with transitionend events and the document visibility. Thanks!
Attachment #8556982 - Flags: review?(josea.olivera) → review+
Comment on attachment 8556982 [details] [review] Github pull request Tested and issue solved together with bug 1127386 and the issue that I saw when inititaing a Loop call from Contact details. Excellent work Cristian!! Please merge this patch in master and in 1.1.1 as this is a critical issue that we need to fix also in that branch
Attachment #8556982 - Flags: feedback?(oteo) → feedback+
Whiteboard: [Room1.1.1_Exploratory1] → [Room1.1.1_Exploratory1][loop approved for 1.1.1]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Room1.1.1_Exploratory1][loop approved for 1.1.1] → [Room1.1.1_Exploratory1][loop approved for 1.1.1][In 1.1.1]
See Also: → 1127779
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: