Basic workflow with no add-on ID (Manifest V2)
An add-on ID is usually optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. One advantage of this is that Google Chrome does not recognize the
browser_specific_settings key and shows a warning if you include it.
However, there are some implications of not setting an add-on ID that are described in this section.
Developing and debugging
If your manifest.json does not contain an ID, the extension is assigned a randomly-generated temporary ID when you install it in Firefox through
about:debugging. If you then reload the extension using the "Reload" button, the same ID is used. If you restart Firefox and load the add-on again, it gets a new ID.
If you turn the extension into an
.zip and install it through
about:addons, it will not work. For it to work, you must add the
browser_specific_settings key in
Once you have finished developing the extension, you can package it and submit it to AMO for review and signing. If the packaged extension you upload does not contain an ID, AMO generates one. It's only at this point that the add-on is assigned a permanent ID, which is embedded in the signed packaged extension.
After publication, you don't generally have to deal with the ID. You can continue to develop the add-on without an ID, and when you want to update, upload the new version by visiting the add-on's AMO page. Because you are uploading the add-on through that page, AMO knows that this is an update to the add-on, even though it doesn't contain an ID.
With this workflow, you must update the add-on manually using its page on AMO. Otherwise, AMO does not understand that the submission is an update to an existing add-on and treats the update as a new add-on.