Closed
Bug 833780
Opened 11 years ago
Closed 11 years ago
[COST CONTROL] No error is shown when you try to topup with an incorrect topup code
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.0 fixed)
RESOLVED
FIXED
blocking-b2g | tef+ |
People
(Reporter: carlosmartinez, Assigned: salva)
Details
(Whiteboard: QARegressExclude)
Attachments
(1 file)
Tested in unagi with Gecko-6a506d1 Gaia-1890022. STR: 1-Pull down notification tray with a prepaid VIVO SIM inserted on the device 2-Tap in topup with code 3-Introduce a number (e.g. "12345678901234") 4-Press send Expected result --> Some kind of error message (e.g. "Incorrect topup code entered") Actual result --> No error is shown
Comment 1•11 years ago
|
||
Blocking because this is a showcase feature for the target markets, and a HUGE annoyance for daily use when topping-up. This is exactly the kind of scenario that turns a delight feature into a papercut.
blocking-b2g: tef? → tef+
Updated•11 years ago
|
Assignee: nobody → salva
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #705870 -
Flags: review?(francisco.jordano)
Comment 3•11 years ago
|
||
Comment on attachment 705870 [details]
Adding a desktop notification when receiving a top up error
Code looking well, tried on the phone with a prepaid vivo sim and fix the bug ;)
Good job Salva, adding :stas for review as we are modifying some strings.
Attachment #705870 -
Flags: review?(stas)
Attachment #705870 -
Flags: review?(francisco.jordano)
Attachment #705870 -
Flags: review+
Comment 4•11 years ago
|
||
Comment on attachment 705870 [details]
Adding a desktop notification when receiving a top up error
r=me.
Attachment #705870 -
Flags: review?(stas) → review+
Assignee | ||
Comment 5•11 years ago
|
||
Landed on master: https://github.com/mozilla-b2g/gaia/commit/b978ccaf2bd55ff0ce20082dd378069132b6eb29
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
status-b2g18:
--- → fixed
Comment 6•11 years ago
|
||
John can you confirm that this was uplifted to both v1-train and v1.0.0 branches? Now that we have the new status-b2g18-v1.0.0 flag we can distinguish between the two when marking. See https://wiki.mozilla.org/B2G/Triage#Flag_Descriptions
status-b2g18-v1.0.0:
--- → affected
Comment 7•11 years ago
|
||
Yes, it's on v1.0.0 https://github.com/mozilla-b2g/gaia/commit/a7fcd500de29e2af290f752f5ac6bed9a9c376ee Thank you for adding this new flag!
Updated•11 years ago
|
Whiteboard: QARegressExclude
No need to create a TC in Moztrap for this defect.
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•