I have a problem adding a chrome extension to my project using Puppeter
For example, I have a folder where I keep the extension in .crx format
const pathToExtension = path.join(process.cwd(), 'extentions');
That's how I take the path.
After thatI add the path to the arguments
`--disable-extensions-except=${pathToExtension}`,
`--load-extension=${pathToExtension}`,
But when I start the application I get this error
Failed to load extension from: /Users/andrew/Desktop/projects/personal-project/extentions. Manifest file is missing or unreadable
To specify that in that extensions folder I have the extension defined like this
ext.crx
Is there a way to add this extension?
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 had gone through the below post on StackOverflow and I know where the chrome extensions are saved in the directory path, in MAC
Where to find extensions installed folder for Google Chrome on Mac?
But my question was, the directory path usually ends into the directory (which has several files and subdirectories)
Which file under this gives me the actual name of the Extension and its version?
For example say jifpbeccnghkjeaalbbjmodiffmgedin is the extension id folder under /Users/$USER/Library/Application\ Support/Google/Chrome/Default/Extensions/. Which exact file should I look inside here to know the name and version of the extension ?
I need this to write a script , so please don't give GUI based solution. I need it on CLI
You are looking for manifest.json in that file you will find all information about chrome extension
/Users/$USER/Library/Application\ Support/Google/Chrome/Default/Extensions/hash_of_your_selected_extenstion/manifest.json
In developing a WinRT 8.1 app, I think that the Uri has to be only of known file extensions? Is that correct? For example, the following snippet will cause an exception on the GetFileFromApplicationUriAsync call even if this file exists as shown:
Uri uri = new Uri("ms-appx:///Assets/lake800x600.flanker");
StorageFile file = await
StorageFile.GetFileFromApplicationUriAsync(uri).AsTask().ConfigureAwait(false);
However, if I change the file extension and the URI to '.dat' or '.txt' it works fine. Is this a known issue? Why can't I refer to and use files of any extension?
You need to make sure your files are marked as content so they are included in the appx package.
Typical data file types such as .txt and .jpg will default to content, but you'll need to set it explicitly for other file types.
Compare a text file:
And a .dat file:
You can confirm by creating a package (Store.Create app packages...), renaming the .appx to .zip, and opening it to see the files. You can also check the Appx folder created in your app's bin\Debug\Appx directory when you deploy and run from Visual Studio
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.