Closed
Bug 850825
Opened 11 years ago
Closed 11 years ago
Error message displayed during app purchase with carrier billing
Categories
(Marketplace Graveyard :: Payments/Refunds, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-04-18
People
(Reporter: krupa.mozbugs, Assigned: keir)
References
Details
Attachments
(1 file)
90.47 KB,
image/jpeg
|
Details |
This test was done over wifi steps to reproduce: 1. Start the purchase of a paid app on your unagi phone 2. Log in using Identity 3. Enter PIN 4. Confirm your mobile phone (AT&T number used) 5. In the Confirm your purchase screen, click on "Buy" screen observed behavior: There is an error message- "The server method 'DoOperatorPaymentWithPrice' failed."is displayed Clicking the Buy button again usually completes the purchase. Also, I don't see any errors in the http log.
Reporter | ||
Updated•11 years ago
|
Version: 1.0 → 1.2
Comment 1•11 years ago
|
||
If this is a transient error, we should provide some info and instructions to the user like "You have not been charged. Please try again"
Reporter | ||
Comment 2•11 years ago
|
||
I can reproduce this by clicking the "buy" button twice.
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•11 years ago
|
||
steps to reproduce: 1. Start the purchase of a paid app on your unagi phone 2. Log in using Identity 3. Enter PIN 4. Confirm your mobile phone (AT&T number used) 5. In the Confirm your purchase screen, click on "Buy" screen 6. While the request is still being sent, click on the "Pay using your credit card" link observed behavior: "The server method 'DoOperatorPaymentWithPrice' failed." error message is displayed
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Whiteboard: [eta 4/3]
Comment 4•11 years ago
|
||
Will be fixed as part of UI changes which Keir is reviewing with Maureen on 12th April to be confirmed when it will make it to test environment
Updated•11 years ago
|
Whiteboard: [eta 4/3]
Comment 5•11 years ago
|
||
To be deployed by 18th April latest for testing work week 22nd April
Assignee | ||
Comment 6•11 years ago
|
||
This has been fixed as of today.
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → 2013-04-18
You need to log in
before you can comment on or make changes to this bug.
Description
•