I have a published google chrome extension. I am trying to find a automated way to query no of new extension installed and create dashboards/reports using that data. So that I can track how the user growth of the extension. I was trying to find a google api that does this but no luck. Appreciate if you have any suggestions / comments on this.
Used google API to query chrome webstore. But no API provides installations / uninstallation statistics
Related
I am working on a Chrome extension running on Chrome OS.
The extension needs the enterprise.hardwarePlatform permission to be able to get hardware information about the device.
The question is: How can I test my extension?
After installing the extension manually, the API to get the hardware information will not work as it needs the extension to be forced-installed by the enterprise policy.
But how to force-install the extension if it is not published in the Chrome Web Store?
Google Workspace seems to allow to refer only to published extensions in the enterprise policy. But obviously I do not want to publish the extension under development. Also I didn't find a "Web Store for development" where I could upload the extension and then refer to it from the policy.
So how to do this?
I found this question:
https://support.google.com/chrome/a/thread/107510644/how-do-i-develop-a-chrome-extension-with-enterprise-permissions?hl=en-gb
However, did not find the answer in any of the provided links. All information seem to point to publishing on Chrome Web Store first. But then would it be impossible to manually test a feature like this before publishing?
Thank you for your answers in advance.
I am pretty much new to chrome extension programming. I have a website which stores data in the localStorage tab of chrome debug tools under Applications with a key of activities. I want to access this into my custom made chrome extension and use it to download that data as a file. Please guide me. Any help is appreciated.
I am extremely confused by popup, background script, content script, etc.
P.S. The data is not stored by me, it is stored by the website I am trying to use this extension on.
I have published a private extension to Chrome webstore. Only people with URL can download this extension.
Some of the users in my organization want to switch to the older version of the extension for sometime. what is the best way to do?
I am aware that chrome webstore doesn't support multiple versions on the same URL.
Sending .crx file is not an option (due to the bug https://bugs.chromium.org/p/chromium/issues/detail?id=638725)
I was thinking to publish the older version of the plugin (with different ID) to the store and give them the new link to download. Does the webstore allow?
are there other ways to do this?
I was thinking to publish the older version of the plugin (with different ID) to the store and give them the new link to download. Does the webstore allow this?
Yes, there should be no problem, especially for the same developer account. It's not atypical to have a "stable" and "testing" versions of the same extension in the Store.
Consider making a mechanism to migrate user settings before you do this (for example, using External Messaging between the two versions or some sort of copy-paste export/import).
I have a Chrome extension that uses the chrome.management API to get a list of installed Chrome extensions and apps. The problem starts because I also want to use the chrome.syncFileSystem API which only seems to be available to Chrome apps.
If I switch the extension to an app, I can no longer use the chrome.management API. I haven't been able to find an API to access the installed extensions from an app. Any tips?
I don't think you can, not without having both an extension and an app.
Google has a private API to do that, but for public API, they want apps to be as independent as possible from the browser.
I'm making an extension for Google Chrome and I use code for autoupdating. This is because the extension isn't yet in Google Chrome webstore. But in a few days I will upload it to the Webstore and Google says you can use the Webstores autoupdating. But if I don't want to use that, will my app still update by my own server, like the way it does now?
Thanks in advance!!
I agree that docs are not very clear about this:
If you publish your extension using the Chrome Developer Dashboard,
you can ignore this page. You can use the dashboard to release updated
versions of your extension to users, as well as to the Chrome Web
Store.
But, I've tested it myself and your update_url setting in manifest.json will be overridden when you publish your extension via Chrome Web Store (CWS). In other words, publishing to CWS means that you can't use self hosted autoupdating anymore.
The reasons for that, that I could think of, may be as follows:
CWS wants to keep track of each extension stats (i.e. number of users using each extension)
privacy concerns (people don't want you to track them when they update extension)
security concerns (each extension update must go through CWS verification process)
If you want to track people (please don't) use Google Analytics on i.e. background page of your extension.