1295584 - Can't Sign Addon

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[fuckfirefox]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce:

Tried to Sign an Addon the same way I signed a lot of addons before


Actual results:

This Beautiful Error shows up!

JPM [info] Created XPI for signing: C:\Users\ME\AppData\Local\Temp\tmp-unsigned-xpi-6708VM126ehOYE65\uninstallfirefox.xpi
JPM [error] FAIL
Error: Received bad response from the server while requesting https://addons.mozilla.org/api/v3/addons/%40uninstallfirefox/versions/0.0.1/

status: 504
response: {}
headers: {"content-length":"0","connection":"Close"}

    at C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\dist\webpack:\src\amo-client.js:115:15
    at tryCatchReject (C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\node_modules\when\lib\makePromise.js:845:30)
    at runContinuation1 (C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\node_modules\when\lib\makePromise.js:804:4)
    at Fulfilled.when (C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\node_modules\when\lib\makePromise.js:592:4)
    at Pending.run (C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\node_modules\when\lib\makePromise.js:483:13)
    at Scheduler._drain (C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\node_modules\when\lib\Scheduler.js:62:19)
    at Scheduler.drain (C:\Users\ME\AppData\Roaming\npm\node_modules\jpm\node_modules\sign-addon\node_modules\when\lib\Scheduler.js:27:9)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickCallback (node.js:349:13)


Tried the Infamous Web-Based Validator, but the 'Validating xyz' takes forever, I doubt it's even doing anything.


Expected results:

Signed a simple Addon and let me test it without having to download a whole other build of FireFox (Developer Edition / Nightly)

Comment 1

[Justin [:JW_SoftvisionQA]]

I see others similar to this bug in addon validation but it is not accessible.

Comment 2

[Jorge Villalobos [:jorgev] (he/him)]

Please file this issue here: https://github.com/mozilla/addons/issues/new

We're no longer tracking them on Bugzilla.