Discover great apps, games, extensions and themes for Google Chrome. Get more done with the new Google Chrome. A more simple, secure, and faster web browser than ever, with Google’s smarts built-in.
- 2 days ago To update Chrome OS, head to the Settings app on your Chromebook click/tap ‘About Chrome OS’ Below the Google Chrome OS logo it will show your current version. If there’s an update available, Chrome OS should automatically start downloading it, and will give you the option to restart once it’s ready.
- Last Update Check. Program Versions Listed. Avast Free Antivirus. Microsoft's Wunderlist to-do app has been living on borrowed time for.
- An update is available when the update button is visible next to the name of the app. Tap 'Update' to begin updating. If the button instead reads 'Open,' then Chrome is already up-to-date.
This article will explain you how to upgrade an app (also called “extension”) which was installed from the Chrome Web Store on your Chromebit or Chromebox, as the Chrome Web Store is a little bit different than the Google Play Store (market) and than Apple’s AppStore.
Before I start, you must be aware that a Chromebox or a Chromebit may be provisioned. “Provisioned” means that the Chromebox has passed the Chromebox enterprise enrollment which puts it under remote control of the Device Management Console of Google, which allows you to remotely control many aspects of it. One common usage is the Chromebox and Chromebit kiosk mode which allows the device to run a single app for 24/7 as it should, like in Chromebit digital signage app.
In case the Chromebox is provisioned and in Kiosk mode, then once the app was upgraded in the Chrome Web Store by its creator, it will take a couple of hours till the app will be auto updated in each of your enrolled Chromebit and Chromebox units (as long as they are online). This is the default behavior (unless you changed it in the Kiosk settings in the Device Management Console).
It is more challenging, when the device is not enrolled.
In order to upgrade the app, you will need to open the Chrome browser on that Chromebox. So, in case of Chromebox or Chromebit which is in a non-managed Kiosk mode, you’ll have to press the Ctrl + Alt + S while the device boots, in order to temporary exit the Kiosk mode and reach the login page.
After logging into the Chromebit, you need to take the following steps:
1. Open the Chrome browser.
2. In the URL field, type: chrome://extensions
3. Make sure that the “Developer mode” checkbox (in the top right corner of the browser) is checked. If not, check it.
4. A button called “Update Extensions Now” should be around. Click it.
5. The app will be updated and might look as disabled during the update.
6. Scroll down to find the app which you have just upgraded. Make sure it is enabled (the “Enabled” checkbox is checked). If it is not enabled, check it. A popup window might appear, asking you to confirm the app’s permissions. In that case, just click the “Re-enable” button.
7. Log out and then reboot the device.
May the signage be with you!
Nir.
Important: Chrome will be removing support for Chrome Apps on all platforms. Chrome browser and the Chrome Web Store will continue to support extensions. Read the announcement and learn more about migrating your app.
We want extensions and apps to be autoupdated for some of the same reasons as Google Chrome itself: to incorporate bug and security fixes, add new features or performance enhancements, and improve user interfaces.
If you publish using the Chrome Developer Dashboard, you can ignore this page. You can use the dashboard to release updated versions to users, as well as to the Chrome Web Store.
If you want to host somewhere other than the store, keep reading. You should also read Hosting and Packaging.
Warning: As of M33, Windows stable/beta channel users can only download extensions hosted in the Chrome Web Store (see Protecting Windows users from malicious extensions).
Previously when off-store extensions were supported, it was possible to have the native binaries and the extension be updated in lock step. However, extensions hosted on the Chrome Web Store are updated via the Chrome update mechanism which developers do not control. Extension developers should be careful about updating extensions that have a dependency on the native binary (for example, legacy extensions using NPAPI).
Overview #
- A manifest may contain an 'update_url' field, pointing to a location for doing update checks.
- The content returned by an update check is an update manifest XML document listing the latest version of an extension.
Every few hours, the browser checks whether any installed extensions or apps have an update URL. For each one, it makes a request to that URL looking for an update manifest XML file. If the update manifest mentions a version that is more recent than what's installed, the browser downloads and installs the new version. As with manual updates, the new .crx file must be signed with the same private key as the currently installed version.
Note: In order to maintain user privacy, Google Chrome does not send any Cookie headers with autoupdate manifest requests, and ignores any Set-Cookie headers in the responses to those requests.
Update URL #
If you're hosting your own extension or app, you need to add the 'update_url' field to your manifest.json file, like this:
Update manifest #
The update manifest returned by the server should be an XML document that looks like this (highlights indicate parts you should modify):
This XML format is borrowed from that used by Omaha, Google's update infrastructure. See http://code.google.com/p/omaha/ for more details. The extensions system uses the following attributes for the and elements of the update manifest:
appid
The extension or app ID, generated based on a hash of the public key, as described in Packaging. You can find the ID of an extension or Chrome App by going to the Extensions page (chrome://extensions).
Hosted apps, however, are not listed on the Extensions page. You can find the ID of any app using the following steps:
Open the app. You can do this by clicking its icon on the New Tab page.
Open the JavaScript console. You can do this by clicking the wrench icon and choosing Tools > JavaScript Console.
Enter the following expression into the JavaScript console:
chrome.app.getDetails().idThe console shows the app's ID as a quoted string.
codebase
A URL to the .crx file.
version
Used by the client to determine whether it should download the .crx file specified by codebase. It should match the value of 'version' in the .crx file's manifest.json file.
The update manifest XML file may contain information about multiple extensions by including multipleelements.
Testing #
The default update check frequency is several hours, but you can force an update using the Extensions page's Update extensions now button.
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 web server such as Apache, and updating that XML file as you release new versions of your extensions.
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:
.svg/1200px-Google_Chrome_icon_(September_2014).svg.png "Chrome"){kind=icon}
?x=_<extension_data>_
Where _<extension_data>_ is a URL-encoded string of the format:
_id=<id>_&v=_<version>_
For example, say you have two extensions, both of which point to the same update URL (http://test.com/extension_updates.php):
- Extension 1
- ID: 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
- Version: '1.1'
- Extension 2
- ID: 'bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb'
- Version: '0.4'
The request to update each individual extension would be:
http://test.com/extension_updates.php?x=id%3Daaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%26v%3D1.1http://test.com/extension_updates.php?x=id%3Dbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb%26v%3D0.4
Multiple extensions can be listed in a single request for each unique update URL. For the above example, if a user has both of the extensions installed, then the two requests are merged into a single request:
http://test.com/extension_updates.php?x=id%3Daaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa%26v%3D1.1&x=id%3Dbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb%26v%3D0.4
Update Chrome Application
If the number of installed extensions using the same update URL is large enough that a GET request URL is too long (over 2000 characters or so), the update check issues additional GET requests as necessary.
Note: In the future, instead of issuing multiple GET requests, a single POST request might be issued with the request parameters in the POST body.
Advanced usage: minimum browser version #
Update Chrome Application
As we add more APIs to the extensions system, it's possible you will want to release an updated version of an extension or app that will work only with newer versions of the browser. While Google Chrome itself is autoupdated, it can take a few days before the majority of the user base has updated to any given new release. To ensure that a given update will apply only to Google Chrome versions at or higher than a specific version, you add the 'prodversionmin' attribute to theelement in your update manifest. For example:
Update Chrome App
This would ensure that users would autoupdate to version 2 only if they are running Google Chrome 3.0.193.0 or greater.