Closed
Bug 1213856
Opened 9 years ago
Closed 9 years ago
Developer Agreement in add-on upload is 404
Categories
(Marketplace Graveyard :: Developer Pages, defect, P1)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mikehenrty, Assigned: chuck)
References
Details
While trying to submit an add-on to the Marketplace add-on submission beta, I get a blank screen. It's most likely because this page is coming back with a 404. https://marketplace.firefox.com/api/v2/account/dev-agreement/show/
Updated•9 years ago
|
Blocks: 1195470
Severity: normal → major
Component: API → Developer Pages
Summary: Developer Agreement is 404 → Developer Agreement in add-on upload is 404
Comment 1•9 years ago
|
||
Also the iframe on https://marketplace.firefox.com/content/dev-agreement (link in the navbar) just shows the Marketplace homepage - I'm guessing its connected.
Assignee | ||
Comment 2•9 years ago
|
||
Production won't be ready for testing until we open up the beta on Wednesday after a push on Tuesday. Resolving as it works fine on staging: https://marketplace.allizom.org/api/v2/account/dev-agreement/show/ https://marketplace.allizom.org/content/dev-agreement
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•9 years ago
|
||
Someone should let the foxfood-mailing list know, since the communication was that this flow should work starting last week.
Comment 4•9 years ago
|
||
(In reply to Chuck Harmston [:chuck] from comment #2) > Production won't be ready for testing until we open up the beta on Wednesday > after a push on Tuesday. The beta for submission started last week. (It would have been open since Wednesday 7th if wasn't for device update issues, but the announcement email went out late Thursday evening)
Updated•9 years ago
|
Assignee: nobody → charmston
Priority: -- → P1
Assignee | ||
Comment 5•9 years ago
|
||
I didn't realize that, my mistake. I made some backwards-incompatible changes across two repos to update this flow, and one got deployed while the other did not.
You need to log in
before you can comment on or make changes to this bug.
Description
•