1203489 - Content Ratings can not be set

Status: VERIFIED FIXED

(Marketplace Graveyard :: Developer Pages, defect, P2)

Description

[Mathieu Pillard [:mat]]

STR:
- Submit an app on -dev
- Go to Content Ratings, click the button to Create a new IARC Certificate
- Fill in the IARC form, click submit

Expected Result:
- The Content Ratings page shows your certificate

Actual Result:
- The Content Ratings page shows a spinner forever, it's calling https://marketplace-dev.allizom.org/api/v1/apps/app/test-app-shark/content-ratings/?since=<date> over and over but it keeps 404ing

Comment 1

[Mathieu Pillard [:mat]]

Note: I worked around it for this app by manually entering the submission code and the security code.

Comment 3

[Mathieu Pillard [:mat]]

Also happens on stage according to QA in bug 1206089

Comment 4

[Mathieu Pillard [:mat]]

Also happens on prod according to QA in bug 1209733

Comment 6

[Valentina Virlics [:vvalentina], Ecosystem QA]

The present behavior is:
- after submitting the content rating for a newly app, the user is taken back to "Content Ratings" page but the page looks like before submission - please check the screenshot: http://screencast.com/t/Eul2MDL5E.
If we navigate from this page to "My Submissions", for instance, the content ratings appears set.
Verified on MP-prod FF44(Win 7).

Comment 7

[Valentina Virlics [:vvalentina], Ecosystem QA]

I observed in MP-stage FF44(Win 7) that if I chose to submit an app with content not recommended under 18, the content ratings are not saved.

Comment 9

[Madalin Cotetiu]

Setting content rating in stage is not working for us. The only scenario when is working is when we set the content rating to PEGI 3 (Selecting no on every single options in the content rating form: http://screencast.com/t/Cyw1Z8kIq3v7)

If we try to create a content rating higher than that it fails: http://screencast.com/t/KWPSsLu6d

Comment 10

[Mathieu Pillard [:mat]]

Not surprising, we need to switch to the new IARC apis to fix that.

Comment 11

[David Durst [:ddurst]]

I'm assuming this is resolved via the new API. This should be checked on dev, and if it passes there, this bug can be verified on Stage after we push the IARC changes to it next week (hopefully).

Comment 12

[Iris Hsiao [:ihsiao]]

Verified on FireFox47 (Win7)
After submitted the IARC form, you will get the Certificate ID on the Content Ratings page.
Closing this bug.