Closed
Bug 1095706
Opened 10 years ago
Closed 10 years ago
[Loop]Firefoxhello! Loop cannot be closed by card view
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
INVALID
People
(Reporter: rmitchell, Unassigned)
References
()
Details
(Whiteboard: [2.1-exploratory-3])
Attachments
(1 file)
273.65 KB,
text/plain
|
Details |
Description: Loop cannot be closed by card view Repro Steps: 1) Update a Flame to 20141107001205 2) Open the loop app and make a loop call 3) In call go to card view and attempt to close Loop via card view Actual: Endless call with other user uninformed Expected: Call screen with and other user is informed of call Environmental Variables: Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash)Build ID: 20141107001205 Gaia: 6295f6acfe91c6ae659712747dd2b9c8f51d0339 Gecko: 8c23b4f2ba29 Version: 34.0 (2.1) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency:100% See attached:logcat,video clip:https://www.youtube.com/watch?v=R_B4oEtdndw
Flags: needinfo?(jmitchell)
This issue DOES occur on 2.2 (319mb)(Kitkat Base)(Shallow Flash) flame 2.0 (319mb)(Kitkat Base)(Shallow Flash) Cannot close app in card view Flame 2.2 Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141107040206 Gaia: 779f05fead3d009f6e7fe713ad0fea16b6f2fb31 Gecko: 64f4392d0bdc Version: 36.0a1 (2.2 Master) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Flame 2.0 Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash BuildID: 20141107000206 Gaia: d3e4da377ee448f9c25f908159480e867dfb13f3 Gecko: 9836e9d81357 Version: 32.0 (2.0) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]: too late in the game to block 2.0 but this seems like some basic functionality that is broken. Poor UX.
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 3•10 years ago
|
||
oteo, can you help assign someone for investigation here. I am not sure if its a cardview issue or something with the app itself, but this is a bad state to be in.
blocking-b2g: 2.1? → 2.1+
Flags: needinfo?(oteo)
Comment 4•10 years ago
|
||
It's working as expected. Once the Loop attention screen is launched the Loop application can not be killed. As you know, we can not kill the Attention screen, as it's part of system and killing system will kill the device. Once the Loop attention screen is launched if we allow to kill the Loop application (the one who has started that Attention screen) all the communication with Loop and his attention screen would be cut and that it will makes the app to crash in that fatal way (The changes in the handling of the attention screen for certified applications were introduced in bug 988212) Some time ago we suffered a partner customization in FireE device that allows killing the Loop application while his attention screen was launched (you can see the details in bug 1085285) and the consequences were fatal, you had to to restart the device to recover it. Of course, The partner had to remove this customization. For that reason, closing the bug as invalid
Status: NEW → RESOLVED
blocking-b2g: 2.1+ → ---
Closed: 10 years ago
Flags: needinfo?(oteo)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•