UpdatingĮven after this point, though, you don't generally have to deal with the ID at all. It's only at this point that the add-on will be assigned a permanent ID, which will be embedded in the signed packaged extension. If the packaged extension you upload does not contain an ID, AMO will generate one for you. Once you have finished developing the extension, you can package it and submit it to AMO for review and signing.

To have it work in this scenario, you will need to add in the browser_specific_settings key in manifest.json. zip and install it through about:addons, it will not work. If you then restart Firefox and load the add-on again, it will get a new ID. If you then reload the extension using the 'Reload' button, the same ID will be used. If your manifest.json does not contain an ID then the extension will be assigned a randomly-generated temporary ID when you install it in Firefox through about:debugging. If you use these APIs in Firefox, then you must set the ID explicitly using the browser_specific_settings key. Note, though, that some WebExtension APIs use the add-on ID and expect it to be the same from one browser session to the next. One advantage of this is that Google Chrome does not recognize the browser_specific_settings key and will show a warning if you include it. If you don't set it, then you can usually develop, debug, publish, and update your extension without ever having to deal with an ID. However, this key is usually optional for Manifest V2 extensions. Removing your extension from distributionīasic workflow with no add-on ID (Manifest V2)Įxtensions can explicitly set the add-on ID using the browser_specific_settings key in manifest.json.Will I ever be able to sell through AMO?.Use plain language in any privacy policy or license agreement.Select the right platforms and versions.The add-on description can be longer, but not too long.Focus on key features in your screenshots.Make sure your summary is just long enough.

Mozilla firefox adons