I have already published a Manifest V2 Chrome native messaging extension in Chrome web store, now I am planning to update it to Manifest V3. However, if I upload and publish the new manifest V3 extension in Chrome web store, the allowed_origins key value will be changed. Because the native messaging host manifest file and native application are two components of the my_software_Setup_verion_01.exe, on the user computers where only the old native messaging manifest file and allowed_origins key value exist, the native application will not start, the new manifest V3 extension on Chrome will not work. Only after the new my_software_Setup_verion_02.exe with the new native messaging host manifest file and new allowed_origins key value is released and installed, the native application can start and the Chrome extension can work.
There is no such issues for Firefox native messaging extension updates, for the allowed_extensions value can be same after the extension updates.
So I want to upload the Manifest V3 extension to Chrome web store to get the new allowed_origins key value but not publish it. Following is the steps:
1, upload the new Manifest V3 extension to Chrome web store to get the new allowed_origins key value, but not publish it.
2, publish or release the my_software_Setup_verion02.exe which includes the new allowed_origins key value in the manifest file, in the new manifest file there are two allowed_origins values, one for the Manifest V2 extension, one for the Manifest V3 extension. So the Manifest V2 native messaging extension will still work.
3, a few days (or weeks) later, I publish the Manifest V3 extension in the Chrome web store. Both the V2 or V3 extension will work.
So the question is: Can I upload the Manifest V3 extension to Chrome web store to get a new allowed_origins key value, and publish the extension in a later time? Thank you!
Related
There are several link checkers in the web store which are using manifest v2. As we don't mention any domain names or rules in manifest v2, these link checkers works fine. In manifest v3, we need to mention the matches in the manifest file.
When i use fetch api in Service worker, it ignores the url if it is not matched with manifest matches
How do we design a manifest so that we can hit any url from the service worker using fetch api?
I tried to add regex patterns, and it works if they are matching. But in link checker, i cannot add all as it can be any link.
I have already installed the google chrome extension Storage Area Explorer in my google chrome browser. Now I can use the Storage Area Explorer google chrome plugin to check the local storage data in the Storage Explorer tab:
but in some plugin extension(the extension was developed by myself and did not publish to google chrome plugin store, the google chrome extension plugin manifest version was v3) page, the Storage Area Explorer did not show.
why did this happen? is it possible to make it show?
We created one chrome extension application and hosted it in the Chrome Store. Now, one of our customers doesn't want their user to download the chrome extension from the store. so, they need group policy distribution so that, the admin(master) will push the chrome extension to their users underneath it. But the problem is that customer use the Linux platform (both admin and all other users). Implementing the group policy in Linux seems not possible (correct me if I am wrong).
It would be helpful if anyone suggests some methods to deploy Chrome extension through group policy like method in the Linux platform.
Firebase Analytics can cover web apps and mobile apps, but is not supported for analytics inside Chrome Web Store. Chrome Platform Analytics seems to be purpose-made for packaged extensions, but I guess won't work for web or mobile components. And then there's good old Google Analytics... hmmm...
In general, it better to create a separate analytics property/tag for each separate medium?
If so, is the data shared across properties?
My Chrome extension has a web component. Should I use one standard Google Analytics tag across both the extension package and web instead of Chrome Platform Analytics? Or would I use Chrome Platform Analytics plus a separate property for the web pages? (note: web used for registration, logging in/out, settings, dashboard)
I intend to create the same extension for other browser platforms. Would I use a different Google Analytics property/tag or the same one across all extensions?
Mobile apps are not yet developed. Should I use Firebase Analytics for these, or what?
Thanks for your input!
The chrome web store support 3 different app types: extensions, hosted apps, and packaged apps. Extensions are for apps that have minimal UI and primarily extend the functionality of Chrome. Packaged apps can run in a tab, can access the Chrome API, and run in the background. Hosted apps run in a tab and require an internet connection to load the page from the host.
But what kind of apps does the G-Suite marketplace support? I noticed that apps installed in the marketplace should up differently (i.e. they show up the nav bar launcher when logged in to Google Apps, not in a Chrome tab) so does that mean there are a different app type? And when Chrome removes support for it's hosted and packaged apps does that also affect the same types of apps in the G-Suite marketplace?
Since your question is more about G-Suite apps but it is worth to know little about other things in chrome store as well.
1. Chrome Extensions:
Chrome extensions are tiny applicatons with minimal ui. You can access all the chrome APIs that you need to create an extension. Take a look at the manifest file or jump over to top section to start learning.
Examples: add blockers and save bookmark extensions
2. Chrome Hosted Apps/ Packaged Apps:
These are Standalone apps with full UI. If you want to give users more interaction or if your app is more complicated with multiple views or it does not interact with user visited web pages then you can choose to create a chrome app otherwise go with extension. You can access all the chrome APIs that you need in your application. One thing to note about hosted Apps, they can't access chrome APIs since they hosted on other servers rather than local to user browser. Here is the manifest file or jump over to top section to start learning.
Examples for Packaged Apps: Rest Clients, Hosted Apps: Messenger apps
If you look extension manifest file and apps manifest file they look identical except you explicitly need to specify it as an app.
So what are chrome APIs: In general you want to access users top most visited websites, there you go you have chrome.history API. You need to specify the permissions in your manifest file before you use them.
Before you choose what you want to create take a look at here. It is just a decision logic which explains which fits for you.
https://developer.chrome.com/webstore/choosing
3. G-Suite Apps:
Google suite Apps are little add-ons to automate the tasks of Google's 11 Cloud Apps. Those apps are Google Docs, Calendar, Drive, Gmail, Translate, Maps etc.Quick intro here.
Since they directly included into google apps so that they can be accessed whenever you use those apps with any browser. You are going to use Javascript (known as App Script here but not much difference) and bunch of google APIs to build your g-suite apps.
Note: They are specifically designed for Google products.
Here are some of your questions:
what kind of apps does the G-Suite marketplace support?
G-Suite apps currently supports product management and education related apps.
I noticed that apps show up the nav bar launcher when logged in to Google Apps, not in a Chrome tab?
Since they are built for google cloud apps they live right inside the apps. You can access them from menu bar. A good example would be a spell checker for docs.
When Chrome removes support for it's hosted and packaged apps does that also affect the same types of apps in the G-Suite marketplace?
As of now, Chrome said they will remove support for in browser chrome apps after mid 2017. But they never told anything about chrome extensions and Google suite apps. So they are safe and Google suite apps are pretty new.