Private extension not auto-updating?

Skip to first unread message

Rajat Paharia

May 1, 2024, 8:57:29 PMMay 1
to Chromium Extensions
Hi all - 

My extension is currently "Published to testers" in Private mode, and I have both a Google Group and a few Trusted Tester accounts added. Nobody seems to be getting automatic updates when I publish a new version to the store, they're having to manually uninstall the old version and then install the new one. Is this expected behavior? 

thanks! - rajat

Patrick Kettner

May 3, 2024, 10:14:54 AMMay 3
to Rajat Paharia, Chromium Extensions
Hi Rajat!
That isn;'t expected. Would you be able to share the extension ID? How long was it between you publishing and them still not having the update? It can take some time for their computer to ping the server and receive the update  (it isn't a push service). If you are still seeing users with this problem, would you be able to see if they can hit the Update button on chrome://extensions and see if it works then?


You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Rajat Paharia

May 3, 2024, 11:27:37 AMMay 3
to Chromium Extensions, Patrick Kettner, Chromium Extensions, Rajat Paharia
Hi Patrick!

The extension id is: gldebcpkoojijledacjeboaehblhfbjg
It was several days after I published the update that my testers said they didn't have the newer version. 
I will see if anyone is still on an older version and can try it.

Thank you! - rajat

Rajat Paharia

May 9, 2024, 11:32:11 AMMay 9
to Chromium Extensions, Rajat Paharia, Patrick Kettner, Chromium Extensions
PSA for anyone else using Extension CLI:
  • The default manifest.json created by Extension CLI includes both a version and version_name, both initially set to 0.0.1
  • By default the build process in Extension CLI overwrites the version in manifest.json with the version from package.json, which is also initially set to 0.0.1
  • But it doesn't overwrite the version_name
  • So I have been happily incrementing the version and version_name in my manifest and uploading new builds which appeared to have increasing version numbers because the version_name was increasing, but in fact all the version numbers were the same 0.0.1
  • Which is probably why my extension was not auto-updating. 
What I did to fix it:
  • I didn't want to have to remember to change the version in package.json when doing any release build. I wanted everything to be in manifest.json. So...
  • I removed the version_name from manifest.json so that this problem could no longer be masked
  • And I removed the line in node_modules > extension-cli > cli > gulpfile.js that copied the version from package.json
    • mft.version = version; // use version from package
- rajat

Rajat Paharia

May 9, 2024, 11:33:07 AMMay 9
to Chromium Extensions, Rajat Paharia, Patrick Kettner, Chromium Extensions
And thanks to Patrick for helping me figure this out! 🙏
Reply all
Reply to author
0 new messages