I'm currently starting develop a chrome extension. But i see that it isn't synced while other extensions that i installed from webstore have been synced to my account.
Could you please show me how to make my extension sync-able. Do they have to upload their extensions to store and register with google to make them sync-able?
Chrome will only sync apps that are published to the web store. For more information on how to integrate your extension's data with sync, see this page: https://developer.chrome.com/extensions/storage.html
Related
I wrote a google chrome extension which should sync data to my chrome profile to all of my computers.
Therefore i'm using the chrome storage api: Google Chrome Storage
I'm able to store and read the data on my primary pc. But on my other computer the data is not accessible.
I'm using the same profile on both computers. And i'm using the chrome.storeage.sync methods.
Because i don't want to publish the extension now i installed the extension with the developer mode activated and not over the chrome store.
Is this the reason why the data is not syncing?
Ok, i now published my app to the chrome store and now it's syncing.
So syncing is not working while your extension is under development.
I have created a small google chrome extension (just a simple html popup)
that itself is a part of desktop app. Now i want to give users ability to install
this extension, but i don't want to publish it to chrome store, as it is not standalone app but only small plugin, that will not work without desktop app installed.
I read here https://developer.chrome.com/extensions/hosting
that i can create .crx file and host in on my own server.
But in same time this page said: "Warning: As of Chrome 33, Windows users can only download extensions hosted in the Chrome Web store, except for installs via enterprise policy or developer mode "
So i am confusing, am i able to create .crx file, host it on my server, and allow windows users install it on their browsers?
Thanks.
Yes with the limitations stated in "Warning: As of Chrome 33, Windows users can only download extensions hosted in the Chrome Web store, except for installs via enterprise policy or developer mode "
Which means that the user cannot download it from any private sever and install it. It has to be installed trough the company GPO and the system need to be joined to an Active Directory domain (A/D).You can download an ADM or ADMX from
https://enterprise.google.com/chrome/chrome-browser
Google is changing Chrome's policy to no longer allow installation of extensions in any way other than through the Chrome Web Store. However, their wording is a little unclear. They state:
We’ll continue to support local extension installs during development as well as installs via Enterprise policy, and Chrome Apps will also continue to be supported normally.
But it's unclear whether they mean ChromeOS apps, or packaged apps as defined by an "app" section in the manifest.json. Do they mean packaged apps can still be installed outside the Chrome store?
http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html
"ChromeOS apps" and "packaged apps as defined by an "app" section in the manifest.json" are one and the same thing. And yes, packaged apps can be installed outside the Chrome Store in their unpackaged form (click the "Development mode" checkbox in chrome://extensions page). Otherwise app development would be seriously hindered.
Our district is starting to use Chrome as a secondary browser. We currently customize a users experience with chrome via the GPO ADM files. However one thing we would like to do is have pre-installed webapps in the Chrome app page. These are simple apps that link to intranet applications and utilities that we use throughout the district.
I know you can force install apps from the chrome web store via the GPO ADM settings, but I don't know if I can apply this process to files hosted in our network.
According to Google's docs it doesn't have to be on the store, but it does have to be hosted somewhere accessible to the box:
Pre-installing via group policy
Using policy to deploy an extension or Chrome web app is the easiest
and most scalable method. This is the recommended method for pushing
extensions,as it does not require the CRX file to be on the machine. It must simply be available at a given URL.
To use this method, set the policy to "force install" the extension,
as described here.
I currently have an extension published in chrome web store.
Now with some additional features, It made more sense to update that to an packaged app.
I have changed the extension to Packaged App.
Now my question is, As I want to retain my current extension users to use Packaged app, Can I directly update the zip file of the New pacakged app to the extension in the chrome store?
Will there be any hiccups in this process? Or do I have to host my new Packaged app separately in web-store (Doing this, I will lose my existing users )?