Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Google Chrome Packaged App - run at system startup

I need to get a Google Packaged App to run at system startup. So, when the OS boots, it automatically loads my app.

Any way to do this in Google Chrome??

Thanks in advance.

like image 666
Imme22009 Avatar asked Jul 26 '13 13:07

Imme22009


People also ask

What is a Chrome packaged app?

A packaged app is a web app that's bundled into a . crx file and can use Chrome extension features. You build a packaged app just like you build an extension, except that a packaged app can't include a browser action or page action. Instead, a packaged app includes at least one HTML file within its .

Where are Chrome apps installed?

When extensions are installed into Chrome they are extracted into the C:\Users\[login_name]\AppData\Local\Google\Chrome\User Data\Default\Extensions folder. Each extension will be stored in its own folder named after the ID of the extension.


1 Answers

If you literally want your app to start up "when the OS boots", then the answer is: You can't.

Otherwise, if it's OK if your app starts when the user logs in, add the "background" permission to your manifest file.

Permission "background"

Makes Chrome start up early and and shut down late, so that apps and extensions can have a longer life.

When any installed hosted app, packaged app, or extension has "background" permission, Chrome runs (invisibly) as soon as the user logs into their computer—before the user launches Chrome. The "background" permission also makes Chrome continue running (even after its last window is closed) until the user explicitly quits Chrome.

The "background" permission is only available for hosted apps, legacy packaged apps and extensions, not for Chrome apps.

If you want to use the "background" permission in a Chrome App, then the only way to do this is to get the extension whitelisted. This can be done using the --whitelisted-extension-id flag:

chromium --whitelisted-extension-id=[YOUREXTENSIONID - 32 chars a-p]

You can only have one extension whitelisted via the command-line, so this should only be used for testing. If you want to publish your app with the background permission, then you're out of luck. The permission was intentionally disabled by the Chromium team, see https://code.google.com/p/chromium/issues/detail?id=163770.

like image 71
Rob W Avatar answered Sep 20 '22 18:09

Rob W