1113448 - [Loop]The option to 'Clean All Rooms' in settings, even if you have multiple rooms created, is grayed out and unresponsive

Status: RESOLVED INVALID

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

Description

[[:RJ]]

Attachment: logcat_20141218_1742.txt

Description:
The option to 'Clean All Rooms' in settings, even if you have multiple rooms created, is grayed out and unresponsive

Repro Steps:
1) Update a Flame to 20141218040201
2) Start a few rooms 
3) Go to loop settings 


Actual:
Even with rooms open clean all rooms button is greyed out  

Expected:
with rooms open, the clear all rooms button is active and can clear all the rooms 

Environmental Variables:
Device: Flame 2.2 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141218040201
Gaia: 58734e8a48157f99d5b733412b600c2e04c954fe
Gecko: 5c7a6294b82a
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 37.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0



Repro frequency:3/3
See attached:Logcat, video clip:https://www.youtube.com/watch?v=W1XP64H6juI

Comment 1

[[:RJ]]

issue was  affected in  2.1 flame or 2.0
greyed out clear rooms even when there are rooms 

Flame 2.1

Environmental Variables:
Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141218001205
Gaia: 14315733e2d265a42f9ab02d1aba191789870f70
Gecko: ddecea83ce6e
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


Flame 2.0
Environmental Variables:
Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
Build ID: 20141218000204
Gaia: d04710d5d643eeff5a6493aef92a1af672a2769c
Gecko: decf1ee4464e
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 2

[Maria Angeles Oteo (:oteo)]

We are still developing Loop master branch (that will be 1.1.1 Loop mobile app version), that's the reason that button is deactivated.

for the time being, let's close the bug as Invalid and we'll let you know when the app is ready to be tested. Thanks a lot for your help!