Home/ Questions/Q 6676847
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T04:02:36+00:00

When we push a new version to our server, the old extensions deployed take

  • 0

When we push a new version to our server, the old extensions deployed take some time (<7hours in the docs, but I have seen more) to update themselves. The problem is that these OLD extensions may talk to the NEW services/api deployed on the server, thus raising conflicts. And those are very hard to hunt down…

Any advice?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can’t force autoupdate but you can pass api version along with the server response and have extension notify users to upgrade if it is outdated (response version doesn’t match hardcoded into extension version).

    UPDATE

    Ok I just reread the question and looks like author is talking about the extension gallery. In this case you can’t just point a user to the gallery as it doesn’t allow you to reinstall an extension without uninstalling first anymore (it used to a while ago). In this case, to force reinstall you would have to either ask users to hit “Refresh now” button on the their chrome://extensions/ page, or download and install your extension’s crx directly, which has the following (scary) format:

    http://clients2.google.com/service/update2/crx?response=redirect&x=id%3D<EXTENSION_ID_HERE>%26uc%26lang%3Den-US&prod=chrome
    • 0