Closed
Bug 1066356
Opened 10 years ago
Closed 10 years ago
Disabled in-app product shows up in the app
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: krupa.mozbugs, Assigned: andy+bugzilla)
References
()
Details
Attachments
(1 file)
97.17 KB,
image/jpeg
|
Details |
steps to reproduce: 1. Load https://marketplace.allizom.org/developers/app/fxpay/in-app-payments/in-app-products/ 2. Notice that one of the in-app products is disabled 3. Install the FxPay app on your FirefoxOS phone 4. Change the API to marketplace.allizom.org 5. Check the list of in-app products listed expected behavior: Only enabled products are listed actual behavior: disabled in-app products are also shown to users. However clicking the buy button for a disabled app returns a 400 and nothing happens.
Comment 1•10 years ago
|
||
I could also reproduce this with https://marketplace.allizom.org/developers/app/in-app-payments-test/in-app-payments/in-app-products/ "Purchasing" index.js:31 "starting purchase for product" "99520ef2-2d94-4107-b2b2-f62bb057c95c" fxpay.js:527 "opening" "POST" "to" "https://marketplace.allizom.org/api/v1/webpay/inapp/prepare/" fxpay.js:793 TypeError: info is undefined index.js:54 "BAD_API_RESPONSE" "status:" 400 "for URL:" "https://marketplace.allizom.org/api/v1/webpay/inapp/prepare/" fxpay.js:763 "BAD_API_RESPONSE" "response:" "{"inapp":["Can not start a purchase on this inapp product."]}"
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → amckay
Assignee | ||
Comment 2•10 years ago
|
||
https://github.com/mozilla/fxpay/pull/34 https://github.com/mozilla/zamboni/pull/2552/files
Assignee | ||
Updated•10 years ago
|
Priority: -- → P3
Assignee | ||
Comment 3•10 years ago
|
||
You'll need an updated fxpay.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 4•10 years ago
|
||
You can grab a new version of fxpay by doing `bower update fxpay` or download 0.0.4 from here: https://github.com/mozilla/fxpay/releases
You need to log in
before you can comment on or make changes to this bug.
Description
•