Closed Bug 957353 Opened 9 years ago Closed 9 years ago
[IARC] content ratings can't be created on -dev pointing to IARC production
STR: 1. Submit an app. 2. Set up content ratings (go through the IARC tool). 3. Click confirm on IARC tool. 4. Go back to the app's content rating page. Expected: The page is refreshed, showing the content ratings summary page. Actual: The spinner keeps spinning, content ratings haven't been created on Marketplace side. Notes: The tool is supposed to hit our API at https://marketplace-dev.allizom.org/api/v1/apps/app/<APP_SLUG>/content-ratings/pingback/, which we pass into the form. I'm not sure what the issue is, is marketplace-dev not whitelisted on the IARC production box?
Alternative STR: 1. Submit an app. 2. Go to content ratings edit page. 3. Input a valid submission ID/security code. Expected: Content ratings are created. Actual: The submission ID and security code is invalid (content ratings aren't returned from the IARC API).
Severity: normal → blocker
Priority: -- → P1
Target Milestone: --- → 2014-01-14
Simon and/or Christine, please respond to this ASAP.
This is probably a Marketplace issue, not an IARC issue. I think we have the Demo instance hard-coded in some locations of our code.
OK. Just let us know if we can assist.
Okay, I fixed calling GET_APP_INFO by pulling down the production WSDL. However, we aren't receiving the pingback to our API after going through the rating tool. We are passing in https://marketplace-dev.allizom.org/api/v1/apps/app/<APP_SLUG>/content-ratings/pingback/ as the pingbackurl to https://www.globalratings.com/IARCPRODRating/Submission.aspx Does the production submission endpoint allow the pingbackurl to come from https://marketplace-dev.allizom.org?
I took a look at this first thing this morning and found on the issue on our end. It has been corrected now, the pingback should be received when completing a submission.
Thanks Christine! Everything is working perfectly now.
Assignee: nobody → kngo
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.