Closed
Bug 1264808
Opened 9 years ago
Closed 9 years ago
Signing API is down
Categories
(addons.mozilla.org :: Security, defect, P1)
addons.mozilla.org
Security
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: emiliano.heyns, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Steps to reproduce:
Trying to sign my extension via the API
Actual results:
The signing status keeps returning "0 files", even if I let it run for 10 minutes. Usually my extension is signed within 30 seconds.
Expected results:
It should have returned files: 1, signed: true and the URL I can download the signed XPI from.
|
Reporter | |
Updated•9 years ago
|
Severity: normal → critical
Priority: -- → P1
Same problem. Signing via jpm sign works, though.
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160511223818
Actual results:
> Your add-on failed validation with 1 error.
> Received an empty response from the server; status: 0
(In reply to kreikenbaumaccoun from comment #1)
> Same problem. Signing via jpm sign works, though.
>
> User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101
> Firefox/46.0
>
> Build ID: 20160511223818
>
> Actual results:
>
> > Your add-on failed validation with 1 error.
> > Received an empty response from the server; status: 0
Very unlikely correlation, but about:troubleshooting shows the "Multi-process staged rollout" extension
|
||
Comment 3•9 years ago
|
||
This is not a security bug. Please file non-security bugs at https://github.com/mozilla/addons/issues .
Thank you.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•