This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can't install addon because it seems to be corrupt

  • 3 پاسخ
  • 6 have this problem
  • 1 view
  • آخرین پاسخ توسّط cor-el

more options

I developed a Firefox addon which is only for users in my company. So I and want to distribute the .xpi file for manual installation. Now, I uploaded the .zip file to addons.mozilla.org where the addon passes the automatic tests and I am able to sign it, which I did. After downloading the .xpi file Firefox says, that the addon can not be installed because it "appears to be corrupt".

I developed a Firefox addon which is only for users in my company. So I and want to distribute the .xpi file for manual installation. Now, I uploaded the .zip file to addons.mozilla.org where the addon passes the automatic tests and I am able to sign it, which I did. After downloading the .xpi file Firefox says, that the addon can not be installed because it "appears to be corrupt".

Chosen solution

OK. I checked the documentation of the manifest.json file and it looks like a missing matches key in the content_scripts object.

Adding this key as a test allows to load the extension via about:debugging.

  "content_scripts": [
    {
      "matches": ["*://*.mozilla.org/*"],
      "js": ["ELiSA.js", "aes.js"],
      "css": ["ELiSA.css"]
    }
  ],
Read this answer in context 👍 1

All Replies (3)

more options

You can find both, the .zip and the .xpi in my dropbox: here

more options

I get the same error (even tried about:debugging in Nightly), so there is definitely something wrong here (manifest.json?).

Maybe consider to ask advice elsewhere.

more options

Chosen Solution

OK. I checked the documentation of the manifest.json file and it looks like a missing matches key in the content_scripts object.

Adding this key as a test allows to load the extension via about:debugging.

  "content_scripts": [
    {
      "matches": ["*://*.mozilla.org/*"],
      "js": ["ELiSA.js", "aes.js"],
      "css": ["ELiSA.css"]
    }
  ],