AutoUpdate

+ +

Home
Getting Started
Overview
Developer's Guide
+
- Toolstrips
- Page Actions
- Background Pages
- Content Scripts
- Events
- Tabs
- Windows
- Bookmarks
- Themes
- NPAPI Plugins
- Cross-Origin XHR
- Packaging
- Autoupdate
+
Tutorials
+
- Debugging
+
Reference +
- Formats +
  - Manifest Files
  - Match Patterns
  - Packages (.crx)
  +
- chrome.* APIs
- Other APIs
+
Samples

+ +

Contents

+ Introduction +
1. + h3Name +
+
+ Overview +
1. + Update URL +
2. + Update Manifest +
3. + Testing +
4. + Advanced Usage : Request Parameters +
5. + Advanced Usage : Minimum Browser Version +
+

+ + + +

AutoUpdate

true

Introduction

We want extensions to be autoupdated for some of the same reasons as chrome itself: to incorporate bug and security fixes, add new features or performance enhancements, and improve user interfaces.

+ +

For extensions packaged and distributed via the extensions gallery, developers will be able to use a web interface to release updated versions of their extensions and do not need to concern themselves with the rest of this document.

+ +

Those who choose to host extensions themselves instead of using the gallery will probably want to use autoupdate for their extensions as described below. You might want to make sure you are familiar with Packaging first.

+ + +

Overview

An extension manifest may contain an "update_url" for doing update checks.
The content returned by an update check is an "update manifest" xml document listing the latest version of an extension (or set of extensions, more on that later).

+ +

Every few hours, the browser will check if any installed extensions have an autoupdate url. For each one, it will make a request to that url looking for an update manifest xml file. If the update manifest mentions a version of an extension that is more recent than what's installed, it will download and install the new version. Similar to manual updates, the new crx must be signed with the same private key as the currently installed version.

+ + +

Update URL

For those who are hosting their own extensions, you need to add the "update_url" key to your manifest.json file like this:

{
+  "name": "Test Extension",
+  "version": "1.0",
+  "description": "My test extension",
+  "update_url": "http://myhost.com/mytestextension/updates.xml",
+  "toolstrips": ["mytoolstrip.html"]
+}
+

+ +

Update Manifest

The "update manifest" returned by the server should be an xml document that looks like this (parts you'll want to modify highlighted):

+ +

<?xml version='1.0' encoding='UTF-8'?>
+<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
+  <app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'>
+    <updatecheck codebase='http://myhost.com/mytestextension/mte_v2.crx' version='2.0' />
+  </app>
+</gupdate>
+

+ +

(This xml format is borrowed from that used by Omaha, Google's update infrastructure. See http://code.google.com/p/omaha/ for more details.)

+ +

appid
+The 'appid' property is the extension id, generated based on a hash of the extension's public key as described in Packaging. You can find out the id of your extension by going to chrome://extensions/ in a chrome browser where you have the extension installed.

+ +

codebase
+The 'codebase' property is a url to the crx file.

+ +

version
+This is used by the client to determine whether it should download the crx file at 'codebase'. It should match the version parameter in the crx file's manifest.json file.

The update manifest xml file may contain information about multiple extensions by including multiple <app> tags.

+ + +

Testing

The default update check frequency is several hours, which obviously makes testing challenging. To overcome this, you can use the --extensions-update-frequency command line flag to set a more frequent interval in seconds. For instance, to make checks run every 45 seconds, you would run chrome like this:

chrome.exe --extensions-update-frequency=45

+ +

Note that this affects checks for all installed extensions, so consider the bandwidth and server load implications of this. You may want to temporarily uninstall all but the one extension you are testing with, and should not run with this option turned on during normal browser usage. In the future we may remove this command flag and replace it with a different mechanism to trigger update checks for testing (perhaps a button on the chrome://extensions page). Star the following issue to receive updates: http://crbug.com/17853.

+ +

Addendum: the "Update now" button has been added, and will be present in dev channel builds soon (likely 4.0.207.x and above).

+ + +

Advanced Usage : Request Parameters

The basic autoupdate mechanism is designed to make the server-side work as easy as just dropping a static xml file onto any plain webserver such as apache, and updating that xml file as you release new versions of your extension(s).

More advanced developers may wish to take advantage of the fact that we add on parameters to the request for the update manifest to indicate the extension id and version. Then they can use the same update_url for all of their extensions pointing to a url running dynamic server side code instead of a static xml file.

The format of the request parameters is:

?x=<extension_data>

where <extension_data> is an url-encoded string of the format:

id=<id>&v=<version>

+ +

So for example, say we have two extensions installed

Extension 1 with id "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" and version "1.1"
+ Extension 2 with id "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb" and version "0.4"

+ +

and that both point at the same update_url: http://test.com/extension_updates.php

+ +

The two requests made would be:

+http://test.com/extension_updates.php?x=id%3Daaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%26v%3D1.1 +
+http://test.com/extension_updates.php?x=id%3Dbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb%26v%3D0.4 + +

Note: in releases before 3.0.196.x there was a bug in how request parameters were put together (http://crbug.com/17469).

+ +

Future work for Request Parameters

While not implemented yet, we will eventually list multiple extensions in a single request for each unique update_url. For the above example, the request would end up being:

http://test.com/extension_updates.php?x=id%3Daaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%26v%3D1.1&x=id%3Dbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb%26v%3D0.4

+ +

If the number of installed extensions using the same update_url is large enough that a GET request url would be too long (probably greater than 1024 characters or so), the update check will instead issue a POST with the request parameters in the POST body.

+ + +

Advanced Usage : Minimum Browser Version

As we add more API's to the extensions system, it's possible you will want to release an updated version of an extension that will only work with newer versions of the chrome browser. While chrome itself is autoupdated, it can take a few days before the majority of the userbase has updated to any given new release. To ensure that a given extension update will only apply to chrome version at or higher than a specific version, you would add the prodversionmin parameter to the <app> tag in your update manifest. For example:

+ +

<?xml version='1.0' encoding='UTF-8'?>
+<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
+  <app appid='aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'>
+    <updatecheck codebase='http://myhost.com/mytestextension/mte_v2.crx' version='2.0' prodversionmin='3.0.193.0'/>
+  </app>
+</gupdate>
+

+ +

This would ensure that users of this extension would only autoupdate to version 2 if they are running chrome 3.0.193.0 or greater.

+ +

+ + +

+ +

API reference: chrome.apiname

+ + +

+ +

Properties

+ +

getLastError

+ + chrome.extensionlastError +

+ +

+ + +

+ +

Methods

+ + +

+ +

method name

+ +

void + + chrome.module.methodName(, + )

+ +

Undocumented.

+ A description from the json schema def of the function goes here. +

+ + +

Parameters

+ + + +

Returns

+ + + +

Callback function

+ If you specify the callback parameter, + it should specify a function that looks like this: +

+ + +

function(Type param1, Type param2) {...});

+ +

+ + +

+ +

Events

+ + +

+ +

event name

+ +

+ + chrome.bookmarksonEvent.addListener(function(Type param1, Type param2) {...}); +

+ +

Undocumented.

+ A description from the json schema def of the event goes here. +

+ + +

Parameters

+ + +

+ +

+ + +

+ +

Types

+ + +

+ +

type name

+ +

AutoUpdate

Introduction

Overview

Update URL

Update Manifest

Testing

Advanced Usage : Request Parameters

Future work for Request Parameters

Advanced Usage : Minimum Browser Version

API reference: chrome.apiname

Properties

getLastError

Methods

method name

Parameters

Returns

Callback function

Events

event name

Parameters

Types

type name

Parameters

Parameters

Get your browser ready

Create and load an extension

Create and load an extension

Introduction

Overview

Update URL

Update Manifest

Testing

Advanced Usage : Request Parameters

Future work for Request Parameters

Advanced Usage : Minimum Browser Version