Web-ext signing error

Add-ons Development
#1

Hi everyone,
We were using web-ext@7.8.0 to sign and test our addon, it worked smoothly before
Since this Monday, we are getting the error as below

2023-12-04 21:30:15 IMPORTANT: web-ext v8 will introduce a new AMO submission API for signing and you might need to take actions when upgrading from v7 to v8. You can test this upcoming change now by specifying `--use-submission-api` to the `sign` command. If you want to keep using the API you are using now (via "sign-addon"), you must stay on v7.
2023-12-04 21:30:20 Server response: Some features are temporarily disabled while we perform website maintenance. We'll be back to full capacity shortly. (status: 503)
2023-12-04 21:30:20 FAIL
2023-12-04 21:30:20 
2023-12-04 21:30:20 WebExtError: The extension could not be signed
2023-12-04 21:30:20     at file:///root/.nvm/versions/node/v20.9.0/lib/node_modules/web-ext/lib/cmd/sign.js:156:13
2023-12-04 21:30:20     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-12-04 21:30:20     at async Program.execute (file:///root/.nvm/versions/node/v20.9.0/lib/node_modules/web-ext/lib/program.js:268:7)
2023-12-04 21:30:20     at async file:///root/.nvm/versions/node/v20.9.0/lib/node_modules/web-ext/bin/web-ext.js:13:1

Just would like to confirm is it the signing server issue? We should just wait for AMO maintenance to finish?

Thanks a lot!

#2

Signing is successful now, sorry about the question.
It would be better Mozilla can have a service status site like https://www.githubstatus.com/

#3

Me hoping this is some kind of action taken to stop the recent flood of “spam extensions”. Though more likely I guess, it is “just” some preparation of serving extensions for the Firefox Android browser.

#4

Thanks Stig,
I am not sure it was an AMO routine maintenance or due to the recent spam extensions.

And I just learned recently that the signing API also has a rate-limit, if you sign too frequent, server will return 429 and you have to wait more than 30min. But honestly, the rate-limit can not prevent the spam extension at all.