Closed
Bug 1037039
Opened 10 years ago
Closed 10 years ago
[B2G][Cost Control][OTA] After OTA the Usage app goes through the FTE again
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: jschmitt, Unassigned)
Details
Attachments
(1 file)
275.96 KB,
text/plain
|
Details |
Description: The Usage app makes the user proceed through the FTE for Usage app after OTA Repro Steps: 1) Update a Flame to 20140710000201 2) Open the Usage app 3) Proceed through the Usage apps FTE and set a Wifi/Data limit with an alert on every 27th day 4) Download and Install the System update 5) Unlock screen, open Usage app Actual: User has to setup the Usage app again. Expected: The Usage app does not make the user go through first time setup a 2nd time. Environmental Variables: Device: Flame 2.0 Build ID: 20140710000201 Gaia: 35a9b715e7348ec738ff6c8a59f50190390a06f2 Gecko: 94714370dfc3 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Notes: Repro frequency: 100% See attached: logcat
Reporter | ||
Updated•10 years ago
|
Updated•10 years ago
|
QA Contact: ddixon
Comment 1•10 years ago
|
||
This issue was found migrating 2.0 -> 2.0. I personally tested 1.3 -> 2.0 by placing latest 1.3 gaia on top of v122 base image. The issue did not reproduce with this method for 1.3 -> 2.0. Adding qawanted to find 1.4 -> 1.4, 1.4 -> 2.0.
Updated•10 years ago
|
Comment 2•10 years ago
|
||
Issue DOES NOT reproduce when migrating from 1.4 to 2.0 Flame build. QAwanted request to find a 1.4 to 1.4 migration was determined to be an invalid action. (comment 1) Environmental Variables: Device: Flame 2.0 Build ID: 20140716000201 Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6 Gecko: 913827496f65 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Comment 3•10 years ago
|
||
not nomming, replaying the FTU after OTA does not seem significant
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 4•10 years ago
|
||
Can we double check this now, with the latest versions of the platform?
Keywords: qawanted
Comment 5•10 years ago
|
||
Bug DOES NOT occur when user updates their device from Flame 2.0-->2.0, 2.0-->2.1 and 2.1-->2.2 (Full Flash, nightly, 319 MB memory). Actual Results: Usage app retains the settings that the user applied before and after an OTA update. Device: Flame 2.2 BuildID: 20141107073659 Gaia: 779f05fead3d009f6e7fe713ad0fea16b6f2fb31 Gecko: b62ccf3228ba Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 36.0a1 (2.2) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 Device: Flame 2.1 BuildID: 20141107001205 Gaia: 6295f6acfe91c6ae659712747dd2b9c8f51d0339 Gecko: 8c23b4f2ba29 Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 34.0 (2.1) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.0 BuildID: 20141107000206 Gaia: d3e4da377ee448f9c25f908159480e867dfb13f3 Gecko: 9836e9d81357 Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89 Version: 32.0 (2.0) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ddixon
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•