Closed
Bug 867729
Opened 11 years ago
Closed 11 years ago
Hook up payments to Fireplace
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-05-09
People
(Reporter: krupa.mozbugs, Assigned: basta)
References
Details
We need to work payments works with Fireplace seamlessly. Please hook up payments asap since we have people waiting to make release decisions.
Updated•11 years ago
|
Component: Payments/Refunds → Consumer Pages
Assignee | ||
Comment 1•11 years ago
|
||
How do we test this? Is there documentation?
Comment 2•11 years ago
|
||
Sure, you can generate a simulation key per the documentation -- https://developer.mozilla.org/en-US/docs/Apps/Publishing/In-app_payments -- then you can use this tester app http://inapp-pay-test.farmdev.com/ at http://inapp-pay-test.farmdev.com/manifest.webapp You need to push these preferences to the device https://github.com/mozilla/webpay/blob/master/ezboot/custom-prefs.js (to /data/local/user.js). Or you can put that in build/custom-prefs.js when you build a gaia profile for desktop b2g. To test it, do {'simulate': {'result': 'postback'}} You can also generate a real payments key after submitting a paid app and that should work too on dev or stage.
Comment 3•11 years ago
|
||
Sorry, you were asking how to test marketplace payments specifically. Just make sure the prefs are correct then purchase an app. I can help you find which zamboni settings correlate to the device prefs
Assignee | ||
Comment 4•11 years ago
|
||
https://github.com/mozilla/fireplace/commit/7c7c5b4ae16a150994b1f30150241cbd8026e81d This adds the ability to trigger the payment flow and check that the app was paid for. There are rough edges, but this "mostly works".
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee: nobody → mattbasta
Target Milestone: --- → 2013-05-09
You need to log in
before you can comment on or make changes to this bug.
Description
•