I made some changes to a Chrome Extension of mine, I updated the manifest.json by changing the extension's version number and, finally, I uploaded it to the Chrome Web Store.
Here is the url.
Now if you try to install it, you'll get an "invalid manifest" error.
The problem here is that I don't either get this error with the locally unpacked version or when I upload the extesion to the Chrome Web Store.
This is the manifest.json
Related
I'm building an internal extension for my company. Since it's an internal tool, I don't want to publish it on the Chrome Web Store.
To be able to self-host the browser extension, I'm doing the following steps:
(before): I created a .pem to sign the extension (+ keep a constant extension id across updates)
I'm building the source code
I'm packing and signing the extension with chrome using chromium --pack-extension=./build_dir/ --pack-extension-key=./key.pem
I'm updating the update.xml file to reflect the new version number
I uploaded the signed .crx and update.xml
I have a website with a link pointing to the .crx file. The issue is the following: when clicking on it, the file is downloaded and chrome understands it's a browser extension. Then: I'm getting "Package is invalid crx_required_proof_missing".
What am I missing?
What can I do to be able to install a self-hosted extension after downloading the extension?
Notes:
I am aware that I can extract the .crx content and load the extension as "unpacked", but that's not what I'm looking for: deployment will be more complex (more manual steps) and updates will not be automatic.
The .crx file seems to be served with the right headers and is publically accessible. The update file is also correct and accessible.
Info:
Yes, the manifest contains properties key and update_url.
When dragging/dropping the .crx file in chrome://extensions (in dev mode): the extension is installed but I'm getting a red warning on the extension card: "This extension is not listed in the Chrome Web Store and may have been added without your knowledge"
When dragging/dropping the .crx file in chrome://extensions (without dev mode):
The extension is not installed and I'm getting: "Package is invalid crx_required_proof_missing".
When dragging/dropping the .crx file in chrome://extensions (with CHROMIUM and dev mode):
The extension is properly installed and working.
Currently trying to add a new extension via the Chrome developer dashboard but getting the below error when I try to upload the zipped folder.
No manifest found in package. Please make sure to put manifest.json at
the root directory of the zip package.
This is what's inside the zipped folder, which as you can see, has the manifest in it's root.
The manifest is v3 and everything works fine unpacked in the extensions developer mode when I'm testing it.
Any ideas what I'm missing here?
It turns out it was as simple as the name of the manifest being Manifest and not manifest... the capitalised M made all the difference...
there's a day of my life I'm not getting back.
I try to auto-install a chrome extension on a WIN10 device that have no connection to the internet and thus can not access the Chrome Web Store. So uploading the extension to the CWS is no option. The extension exists as a crx file on a server in a network and on the device.
On Chrome Versions 59 and lower I could install the extension via settings in the registry. When Chrome was started, the user was ask if he wants to install the extension.
For this I used the registry key ExtensionInstallWhitelist and defined the path and version of the extension under the key "[...]/Google/Chrome/Extensions/[ExtensionID]".
But since Version 60 the extension does not appear in Chrome anymore. So I tried to auto-install the extension via an Active Directory domain policy.
I have imported the chrome policy templates and configured the entry ExtensionInstallForcelist (http://www.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist) in the group policy editor. This policy setting is listed on the chrome://policy page in Chrome. But the extension does not appear in Chrome. The ExtensionInstallForcelist entry contains "[ExtensionID];[url where the crx file resides]". I also tested this with an url to an "Update Manifest XML document" which points to the crx file. Neither of them worked.
Does anyone know, if Chrome 60+ still supports this?
Is my configuration incorrect?
Any help will be appreciated, thanks!
I'm running into an issue with my Chrome extension on OSX computers only. It used to work fine, but with my latest release, I have a lot of files that I organized into folders (css, js, and img). The extension installs just fine on Windows computers (which is the OS I created the extension on, Windows 7) but when I attempt to install on a Mac I get the message outlined below:
"Package is invalid. Details: 'Could not load extension icon 'img\icon_16.png'.'.
I know the image is there, but my guess is that because I did this on Windows, OSX doesn't like the pathing options. Any ideas how I can rectify this and still keep the folder organization?
Late, I'm aware, but the solution to this was the slash in img\, reversed it and it worked fine.
In my case the problem was that Google Play allows zip with .crx file.
So on first attempt it said me to zip my crx (after crx upload try), then it said that it needs manifest file inside the zip file.
After that everything was fine except of extension installation - it threw out error like "Could not load extension icon".
So the solution is to compress src directory (in which manifest file lays) without packing extension into crx.
I have uploaded a chrome extension on webstore but lost the local from my desktop. Is there any way to download the extension back either from webstore or developer dashboard such that I get all my files?
Just install it and then go to your User Data directory.....
http://www.chromium.org/user-experience/user-data-directory
..then into the directory of the profile you installed it under, then the extensions directory and then the directory with the key of your extension, then the directory with the latest version and youll find all your files. You can find the key listed on the extension page in chrome in developer mode. Dont forget to edit the manifest, remove the update url and such.
Or if your on windows (I know it works in XP, never tested vista/7) you can use my convenience tool ExtensionOpener.....
http://forum.valorsolo.com/viewtopic.php?f=35&t=269&p=1163