Closed
Bug 771664
Opened 13 years ago
Closed 13 years ago
Automatic refunds are failing
Categories
(Marketplace Graveyard :: Payments/Refunds, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: krupa.mozbugs, Assigned: andy+bugzilla)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
steps to reproduce:
1. Purchase https://marketplace-dev.allizom.org/en-US/app/private-yacht/
2. Immediately after purchase(< 30 minutes), try to get a refund.
expected behavior:
Automatic refund is successful.
observed behavior:
Automatic Refund fails with "A refund cannot be applied for yet. Please try again later. If this error persists contact apps-marketplace@mozilla.org. "
Assignee | ||
Comment 1•13 years ago
|
||
Hmm, this looks like a different error. This means the IPN wasn't in yet.
An error was seen in the logs on the IPN for a refund:
ul 6 14:41:20 dev1.addons.phx1.mozilla.com: [<anon>][173.0.82.126] z.paypal:ERROR bad operand type for unary -: 'unicode'#012<WSGIRequest#012GET:<Que...
Assignee | ||
Comment 2•13 years ago
|
||
The error in comment 1 is fixed at least.
https://github.com/mozilla/zamboni/commit/9e0a9d
Comment 3•13 years ago
|
||
This bug sounds like there was a delay in the purchase confirmation. The message clearly stated the problem and the solution. That sounds like as good as this is going to get so I'm going to close the bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•13 years ago
|
||
I think this is because the pay check was marking the payment as completed in solitude. So the IPN got ignored by solitude and zamboni didn't update the contribution so allowing refunds.
I think I got this in:
https://github.com/mozilla/solitude/commit/19caf04fa1b54bedd45ec39da9c9cd8257fdddbb
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•13 years ago
|
||
Yep think that's it.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•13 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•