I'm trying to pack an extension into a .crx, but I get Manifest is unreadable or missing. What does this mean and what can I do?
Related
Hi I'm running VSCode on my mac and Windows 10 machine. They've both started displaying the same symptoms after the latest update/rollback.
Every couple of keypresses I get the output box appear, with the "HTML Language Server" selected in the dropdown. The error displayed is:
[Error - 13:47:09] Request textDocument/documentLink failed.
Message: Request textDocument/documentLink failed with message: Path must be a string. Received undefined
Code: -32603
This gets repeated indefinetly and is making VSCode unusable. I'm editing some JSP / JSTL files so I'm wondering if it's some non-valid HTML setting it off, but this has never been an issue before.
All research I've found of this error seems to suggest a faulty extension, but I've currently not got any installed.
Help appreciated!
This is a known issue and, as per this Github issue, the workaround is to open Visual Studio Code on a folder instead of a file.
I too had this popping up this morning, google pointed me to vscode's extensions, so I went through the vscode extensions, updated them all and Debugger for Chrome (2.2.0) was the only one fitting the Error message.
Since I do not have the time right now to file an issue (and answer follow-ups) on https://github.com/Microsoft/vscode-chrome-debug/issues I have just disabled the extension for now.
One thing to note is, while vscode says it is version 2.2.2 in the extension panel, it is 2.2.0 on its marketplace page and github. Might be of some interest to dive in and find out where the extension panel picks up its - false - version number - and find out whether this has some impact on creating the error.
My Chrome debug console tends to be full of lines like this:
Denying load of chrome-extension://ganlifbpkcplnldliibcbegplfmcfigp/scripts/vendor/jquery/jquery.min.map. Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.
How can I find the source of the complaint?
EDIT For clarity: I don't know what extension is causing this. I have dozens installed. The log is not very helpful.
As said by Rob Wu, this is a chrome bug, and it has been reported by him HERE.
By the way, as long as the bug isn't solved, if you are experiencing this issue you'll only need to add the resources that are causing it to your "web_accessible_resources" field in your manifest.
Plus, if you don't know the extension that is causing this, you can find its ID in the console error log, contained in the URL of the resource:
chrome-extension://<extension-id>/path/to/some_file.js
To identify the extension you can then copy the extension ID and go to the extension page chrome://extensions, then enable developer mode checking the box on the top right part of the page and find the ID of the extension either memorizing part of it or pasting it into the search field hitting CTRL+F.
Avast Bank Mode can stop viewing mp4 and .H264 files. Works in normal Chrome Browser, and not in the Bank Mode.
i build chrome extension and i use NPAPI to open exe file.
To open the file i need full path(C:\Program Files\test.exe).
I attach the "test.exe" to my project and i want to open it.
The problem is that i can't know where the file after the installation.
I need to get something like this:
C:\Users\**User Name**\AppData\Local\Google\Chrome\User Data\Default\Extensions\**App Name**\**App Version**\test.exe
How can i get this?
(All I can found is the "App Name" and the "App Version")
I'm trying to create an install package of my extension. It uses chrome.experimental.sidebar API. When I create the package and install it, everything works just after teh install. When I restart Chrome I cannot open the sidebar - it doesn't show. The onclick method works - I've added an alert to show at the end of it.
I turned on using experimental API in chrome://flags. When I use the extension installed in a folder everything works great.
Am I doing something wrong or does Chrome disallow using expermiental API from packages?
Can you include the manifest file that you're using? Chrome has a known bug where an empty manifest value (e.g. "sidebar" : {}) will not be preserved across restarts. Adding a dummy value inside the sidebar dictionary should prevent this.
I'm trying to automate packaging of the Chrome extension on Windows and according to the documentation, it is this command:
[path]\chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem --no-message-box
However this command results in a new browser window and no action is performed. I tried other switches like --version or --help but it seems that Chrome is ignoring all of this. Do others have the same issue? What am I doing wrong? I also tried various quoting and with no other browser window open but I haven't been able to make this work.
Update: I'm happy to learn that the new Chrome 8 has fixed this issue.
The answer is present in one of the comments. I am reposting the answer verbatim here:
You can try one of the scripts to pack
an extension at
https://developer.chrome.com/extensions/crx#scripts
– by Na7coldwater
You'll need to close all chrome windows before the command line pack extension command will work.
I raised this bug with the chrome team some time ago (http://code.google.com/p/chromium/issues/detail?id=22901) but it's not quite fixed yet. This can be somewhat frustrating because (as michaelhermannweber pointed out) "Since we're fans of Chrome, obviously Chrome is already open!"
I even tried to use a separate instance of the chrome executable to build the extension, but alas no luck on that front either :(
For now, AFAICT you have to do it manually via the pack extension button on the chrome://extensions page.
You might manage to build a script that closes all open chrome windows, builds the extension, and then re-opens chrome. But I doubt that it would be worth it given the number of tab users like to keep open.