Closed
Bug 874389
Opened 11 years ago
Closed 11 years ago
[Cost Control] Widget does not show the FTE message in v1.0.1
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(blocking-b2g:tef+, b2g18 verified, b2g18-v1.0.1 verified)
RESOLVED
FIXED
blocking-b2g | tef+ |
People
(Reporter: salva, Assigned: salva)
Details
(Keywords: regression, Whiteboard: [required_last_cert_round])
Attachments
(2 files)
Bug 868363 introduces a regression in v1.0.1 that prevents the user to see the FTE message in the widget. This is a problem related with the PR in [1]. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=868363#c32
Assignee | ||
Updated•11 years ago
|
Keywords: regression
Updated•11 years ago
|
blocking-b2g: tef? → tef+
Whiteboard: [required_last_cert_round]
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #752134 -
Flags: review?(jmcf)
Updated•11 years ago
|
Attachment #752134 -
Flags: review?(jmcf) → review+
Comment 2•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/42c448bf7baed154b20ead388de2fd9dd25936f6
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 3•11 years ago
|
||
Just to clarify, 42c448bf7baed154b20ead388de2fd9dd25936f6 is a merge commit into 1.0.1.
Comment 4•11 years ago
|
||
The summary of this bug makes it seem like there is no further action to take on this bug. Is that correct?
status-b2g18-v1.0.1:
--- → fixed
Flags: needinfo?(salva)
Comment 6•11 years ago
|
||
marking as status-b2g18:fixed, even though there was no fix on v1-train to get it out of the uplift queries.
status-b2g18:
--- → fixed
Comment 7•11 years ago
|
||
In V.1.0.1 and V.1.1, the user sees "New SIM inserted. Tap to track your internet usage". Verified on Inari Build ID: 20130530070213 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/11b55d3ada71 Gaia: ac293ce59acc3bede083fad1b973794fa8bf0253 Platform version:18 Unagi Build ID: 20130530070208 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/09ac1fd2959c Gaia: 1cca9324d4444ad28c6fa99875e17abf7e8230be Platform version:18
You need to log in
before you can comment on or make changes to this bug.
Description
•