If multiple parameters are listed, the return value will be a map keyed by the parameter names. If just one parameter is listed, its value will become the value of the input step. Although I think I have read somewhere that saying a manifest file should utf-8 encoded, I saved my mf file to ANSI with Notepad of Windows, and JAR just stopped complaining about the header. So I guess its the BOM of a utf-8 file makes Jar cant understand. This way you won't have to always keep that extension unpacked somewhere. Request that the submitter specify one or more parameter values when approving. Its always the first manifest header makes JAR throw an invalid header IOException. So, after unpacking extension in an old format (as described in another answer) you could pack it back with your current Chrome version and then install it as usual. However, it seems like in Chrome 73 Google forced this change for new installations already and introduced a policy option for updates only. And, new installations of the extension will fail. If your organization is force-installing privately hosted extensions packaged in CRX2 format and you don’t repackage them, they’ll stop updating in Chrome 75. UPDATE 1: If you get a Package is invalid ‘CRXHEADERINVALID. Chrome extensions are packaged in CRX files and they can be manually downloaded from the Google Web Store. Name of the request header optionally providing the token cookie value instead of the HTTP. Privately hosted extensions that were packaged using a custom script or a version of Chrome prior to Chrome. Step 1 Download the Chrome Extension’s CRX file. Starting with Chrome 75, all force-installed extensions will need to be packaged in the CRX3 format. If you right-click on that then you should see View linked extension source in the menu (thats added by the CRX Viewer extension). All extensions must be packaged with CRX3 format in Chrome 75.This problem was reported on and closed as an intended behavior.Īccording to Chrome Enterprise release notes:

Crx header invalid