Question about extension IDs

Eric Bixby eric.k.bixby at
Sat Sep 30 23:16:37 UTC 2017

Check out this example code:

In the hybrid or embedded web-extension, you keep your existing id in your
package.json.  Upload this version to AMO as normal.

Then when you create your web-extension version, move the id to the
manifest.json file.  Upload this version to AMO as normal.  However, once
you switch your add-on to be a web-extension, you cannot switch back.

On Sat, Sep 30, 2017 at 2:09 AM, Neil Bird <lists at> wrote:

>   Well, two questions actually, but I rather suspect I can guess the
> answer to the second :-/
>   I have a “legacy” add-on I finally have a little time to investigate
> porting (although it appears I have less time than I thought due to the
> preferences situation, about which I'll send another post).
>   It has a UUID as an extension ID.  Would the AMO site cope with me
> uploading a new version with a new-style ID, or is it fixed?  I don't
> want to break automatic updates of it.
>   If I can, do I just upload with a new preferred ID against the old
> extension page's “upload new version”?
>   And the follow-up question:  my extension currently supports both
> Firefox and Thunderbird.  Obviously, if I change it to WebExtensions, I
> can't keep the two the same.  Is there anything I can do about this?
> Say, upload a forked Thunderbird version (that's if there are any
> changes in the future) under a new name/UID *but allow existing
> Thunderbird users to auto-update to it*?
> --
> [phoenix at fnx ~]# rm -f .signature
> [phoenix at fnx ~]# ls -l .signature
> ls: .signature: No such file or directory
> [phoenix at fnx ~]# exit
> _______________________________________________
> Webextensions-support mailing list
> Webextensions-support at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Webextensions-support mailing list