Closed
Bug 879195
Opened 11 years ago
Closed 11 years ago
If the in app price point is changed to a value greater then 2 an error will be displayed "Unknownpricepoint", "Poland"
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
2013-06-20
People
(Reporter: vikas.nanda, Assigned: andy+bugzilla)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.94 Safari/537.36 Steps to reproduce: If the user enters a price point value of 2 or greater an error message will be displayed which reads "UnknownPricePoint:" Steps to reproduce: 1. Start the in app application 2. Change the pricepoint value to 2 or greater 3. Select call navigator.mozPay() 4. Notice the error message "UnknownPricePoint" Actual results: The user receives an error message which reads "UnknownPricePoint" Expected results: The Payment should successfully go through without error.
Reporter | ||
Comment 1•11 years ago
|
||
Summary: If the in app price point is changed to a value greater then 2 an error will be displayed "Unknownpricepoint" → If the in app price point is changed to a value greater then 2 an error will be displayed "Unknownpricepoint", "Poland"
Updated•11 years ago
|
Blocks: marketplace-payments
Updated•11 years ago
|
Component: General → Payments/Refunds
Version: 1.1 → 1.2
Updated•11 years ago
|
Priority: -- → P1
Comment 2•11 years ago
|
||
we need to make a generic user message here (turn off verbose errors) yet also provide some detail that a developer can use, such as an error code
Updated•11 years ago
|
Priority: P1 → P2
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → amckay
Target Milestone: --- → 2013-06-13
Assignee | ||
Comment 3•11 years ago
|
||
Very similar to bug 878216. I believe all price points are now correct.
Updated•11 years ago
|
Target Milestone: 2013-06-13 → 2013-06-20
Assignee | ||
Comment 4•11 years ago
|
||
Price points are all right from our end.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•