On Apr 28, 5:22 am, Abraham Williams <
4bra...@gmail.com> wrote:
> The ID of an extension is based on the pem key generated when you pack an
> extension. When you pack later versions of the extension the key file will
> make sure the crx file will have the same ID and that existing installs can
> be updated using it. That is the ID to use with autoupdate. The key is
> saved in the same directory as the crx file. It is your responsibility to
> keep the key safe unless you are using the Web Store.
>
> Abraham
> --
> Abraham Williams |
abrah.am |
>
github.com/abraham |
blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>
>
>
>
>
>
>
> On Fri, Apr 27, 2012 at 13:58, Ziyuan Yao <
yaoziy...@gmail.com> wrote:
> > I suppose I should use the packed .crx's extension ID in update.xml.
>
> > I also wonder where Chrome store an extension's public key or ID so
> > that the next time it packs an updated version of the same extension
> > it will know the public key and write it to the new .crx file?
>
> > On Apr 28, 4:54 am, Ziyuan Yao <
yaoziy...@gmail.com> wrote:
> > > In the Chrome profile that develops my extension, the Extension
> > > Manager says the unpacked extension's ID is
> > > ipfammnpnfdipnoghpmcdkicpijdidhb.
>
> > > Then I packed the unpacked extension to a .crx file. I installed
> > > that .crx file in a new Chrome profile, and the new profile's
> > > Extension Manager says the installed extension's ID is
> > > oohplmnpniglbaibglmnikgkkoanpino.
>
> > > I'm confused. Which ID should I use in an autoupdate xml file?
>
> > > Also, it seems, whichever ID I use, the autoupdate doesn't work.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Chromium-extensions" group.