I've blogged about this hereThis is caused due to the CRX format of the browser used to package the extension for distribution being different from the CRX format being used by your browser.I had this issue when packaging an extension in Chrome 67 for a client using Chrome 57.The solution to the problem is to find out what version of Chrome the target user is using and package your extension with that version. Having looked at the source code it looks like Chrome 67 is supporting CRX2 and CRX3 formats.
I imagine earlier versions of chrome were using CRX1.When an extension is distributed by the Chrome store you do not experience this problem as they are able to send you a signed package using the CRX version as required by your browser version.
In this video clip, we are going to see an issue that I ran into as a result of adding the IDM extension to Google Chrome, and how to easily fix it. For the quick and impatient, follow these steps: (1) Download and Install IDM from the following site. # # The testing repositories are disabled by default. To enable, uncomment the # repo name header and Include lines. You can add preferred servers immediately # after the header, and they will be used before the default mirrors.