Confirmed users
656
edits
EngineeringProductivity/HowTo/SignExtensions: Difference between revisions
EngineeringProductivity/HowTo/SignExtensions (view source)
Revision as of 14:47, 26 February 2016
, 26 February 2016→Common Footguns
No edit summary |
|||
| Line 35: | Line 35: | ||
* After an addon is signed by one key, it can't later be signed by a second. So it's important to use the shared automation account. | * After an addon is signed by one key, it can't later be signed by a second. So it's important to use the shared automation account. | ||
* If you have accidentally signed an add-on yourself, AMO allows an add-on to be shared by multiple owners. Go to addons.mozilla.org > Tools > Manage My Submissions > [Your add-on] > Manage Authors and add "release+signaddons@mozilla.com" as an owner. | * If you have accidentally signed an add-on yourself, AMO allows an add-on to be shared by multiple owners. Go to addons.mozilla.org > Tools > Manage My Submissions > [Your add-on] > Manage Authors and add "release+signaddons@mozilla.com" as an owner. | ||
* Addons with an application id of "toolkit@mozilla.org" don't currently [https://github.com/mozilla/addons-server/issues/1740 get signed by design on AMO] | * Addons with an application id of "toolkit@mozilla.org" don't currently [https://github.com/mozilla/addons-server/issues/1740 get signed by design on AMO] and jpm won't warn you of this, change the application id to Firefox's uuid. | ||
== How to Avoid Addon Signing == | == How to Avoid Addon Signing == | ||