Closed
Bug 1086208
Opened 10 years ago
Closed 7 years ago
[Loop] Call isn't finished, when Loop application is closed in a device
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: lolimartinezcr, Unassigned)
References
Details
(Whiteboard: [Test-Run1][mobile app][not blocking][tef-triage])
Attachments
(1 file)
(deleted),
image/png
|
Details |
fireE (firee-kk-v2.0-SW2E3-1)
Loop version: 1.1 , 2168965
Prerequisites:
Device A with a contact saved.
Device B with a contact saved.
Device A witn some calls to device B in "Calls" tab.
STRs:
1. Device A makes a call to Device B (though "Calls" tab).
2. Device B answert the call.
3. Once call is established, Device A taps in "home" button (Loop application is in background).
4. Device A taps in "Loop" application again. (while call between A and B is working)
5. Device A taps in "Settings" button in Loop application. (while call between A and B is working)
6. Device A taps in "Log out" button in Loop application. (while call between A and B is working)
Actual result:
Loop is closed in Device A (See attached image), but call is working in Device B.
Expected result:
When Loop is closed in Device A, call is finished.
Comment 1•10 years ago
|
||
The call should be ended after a few seconds. The device B should received a 'connectionDestroyed' event on the session and we close the callscreen. How much time did you wait? It takes a few seconds.
Flags: needinfo?(lolimartinezcr)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(lolimartinezcr)
Summary: [Loop] Call isn't finished, when Loop application is closed in a devive → [Loop] Call isn't finished, when Loop application is closed in a device
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to José Antonio Olivera Ortega [:jaoo] from comment #1)
> The call should be ended after a few seconds. The device B should received a
> 'connectionDestroyed' event on the session and we close the callscreen. How
> much time did you wait? It takes a few seconds.
I have waited two minutes.
Comment 3•10 years ago
|
||
(In reply to Loli (:lolimartinezcr) from comment #2)
> I have waited two minutes.
Too much time, I'll a ni request at me to have a look a it.
Flags: needinfo?(josea.olivera)
Comment 4•10 years ago
|
||
One question Loli, how are you able to make steps 5 and 6? when I press on the Loop application icon in the Homescreen, Loop application is put in foreground for a second but immediately the Loop call screen hides the Loop app, so I am not able to enter in settings and log-out from Loop.
Flags: needinfo?(lolimartinezcr)
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Maria Angeles Oteo (:oteo) from comment #4)
> One question Loli, how are you able to make steps 5 and 6? when I press on
> the Loop application icon in the Homescreen, Loop application is put in
> foreground for a second but immediately the Loop call screen hides the Loop
> app, so I am not able to enter in settings and log-out from Loop.
When you do step 4, you press "Shared link" tab, in this moment Loop application is put in foreground.
Flags: needinfo?(lolimartinezcr)
Comment 6•10 years ago
|
||
Loli, I'm able to reproduce the issue as you reported it on the STR. I'd like to say that hitting this issue is so difficult. The attention screen covers the Loop app and the user has to be so quick on opening settings, hit the log out button and confirm the log out from the app. The call is not finishes, this is true and an issue indeed but I don't see the user achieving log out from the app during a call and in that way. To be realistic I won't block on this issue.
Flags: needinfo?(josea.olivera)
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to José Antonio Olivera Ortega [:jaoo] from comment #6)
> Loli, I'm able to reproduce the issue as you reported it on the STR. I'd
> like to say that hitting this issue is so difficult. The attention screen
> covers the Loop app and the user has to be so quick on opening settings, hit
> the log out button and confirm the log out from the app. The call is not
> finishes, this is true and an issue indeed but I don't see the user
> achieving log out from the app during a call and in that way. To be
> realistic I won't block on this issue.
It is true that you say. But the main problem is if Loop application is put in foreground (When you do step 4, you press "Shared link" tab)
Comment 8•10 years ago
|
||
very corner case, so not blocking
Whiteboard: [Test-Run1] [mobile app] → [Test-Run1][mobile app][not blocking][tef-triage]
Comment 9•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•