Extension not updating

[Zachary “Gamer_Z.” Yaro]

I updated one of my extensions almost a week ago and it still has not been updated in my browser on Windows (7) or Linux (Ubuntu 11.04).  I tried clicking "Update extensions now" on chrome://extensions, but it still stayed at the old version number.  It worked when I uninstalled and reinstalled, but obviously it defeats the purpose of self-updating extensions if my users have to do that for every update.  Obviously the extension in question does not have many users, but I am concerned that this could happen to other extensions I write.  Does anyone know what would cause an extension to refuse to be updated like this?

Thanks!

--Zachary “Gamer_Z.” Yaro

[Nimit Shah]

Did u try reloading the extension? Its a wild guess but worth a try!

[Zachary “Gamer_Z.” Yaro]

I tried using the “Update extensions now” button with no luck.  Uninstalling and reinstalling worked, but my point was that users will not enjoy having to uninstall and reinstall for every update.

—Zachary “Gamer_Z.” Yaro

On May 23, 2011 3:08 AM, "Nimit Shah" <nimit...@gmail.com> wrote:

[Adrian Aichner]

On Mon, May 23, 2011 at 12:17 AM, Zachary “Gamer_Z.” Yaro <zmy...@gmail.com> wrote:

I updated one of my extensions almost a week ago and it still has not been updated in my browser on Windows (7) or Linux (Ubuntu 11.04).  I tried clicking "Update extensions now" on chrome://extensions, but it still stayed at the old version number.  It worked when I uninstalled and reinstalled, but obviously it defeats the purpose of self-updating extensions if my users have to do that for every update.  Obviously the extension in question does not have many users, but I am concerned that this could happen to other extensions I write.  Does anyone know what would cause an extension to refuse to be updated like this?

Hi Zachary, I am only using Unpacked extension so far, but saw similar issues.

I found one major issue in my use model:

Using a reloaded extension on an old webpage target still seems to run the old extension code. Refreshing the target webpage solves the problem for me.

I'd like to hear whether this sounds right to others.

It seems kind of obvious to me now but the docs certainly did not make this stand out for me.

Regards,

Adrian

Thanks!

--Zachary “Gamer_Z.” Yaro

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

--
Adrian Aichner
 mailto:adrian....@gmail.com

[PhistucK]

Zachary is talking about a totally different issue.

☆PhistucK