Closed Bug 849912 Opened 10 years ago Closed 10 years ago

KeyError: amount. Webpay error for successful Bango purchase

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kumar, Assigned: kumar)

References

Details

Severity: normal → critical
Priority: -- → P1
Target Milestone: --- → 2013-03-14
Actually, this happened because our stage servers were out of sync but we fixed that in bug 846930

Jorge, can you try testing it again?

This specific error was fixed a while ago in this revision but the code had not been deployed. https://github.com/mozilla/solitude/commit/570c8fc4
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee: nobody → amckay
Hi Kumar,

we have being with Fernando testing with "Private Yatch" and the error was always that there was a Payment Failure.

Will try again on Monday.

Can you tell us how to get the info from HTTP identity logs?
Best
Hmm, maybe this is something specific to MobileID again. I don't see any errors in our logs.

I run `ezboot http` to capture HTTP logs on device: https://github.com/kumar303/ezboot

This starts up B2G with some env vars then pulls down the log file afterward:
https://github.com/kumar303/ezboot/blob/master/ezboot/__init__.py#L200-L202

More docs are here: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging#Firefox_OS_phones

If you can produce the logs I'd like to take a look.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: amckay → nobody
Assignee: nobody → kumar.mcmillan
Target Milestone: 2013-03-14 → ---
I haven't seen this specific error in our logs for more than 60 days and it didn't come up during the test week so I think we are receiving the right query string from Bango now.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.